RE: Autopackage creation

> And no, bunding the support code will NOT force an upgrade.

> I'm not sure what to do about this. The best solution would be if
> autopackage could update itself, either through the normal
> distribution update mechanism (we actually had hopes about this back
> in the 1.0 days, but reality hit us hard in the head), or through some
> homebrewed auto-updater.

Well, legalizing my hackaround will mostly solve this. Allow package
maker to specify autopackage version with whatever precision needed.

So if any 1.2 will do -- set AutopackageTarget in apspec to 1.2, and if
at least 1.2.3 needed -- set it to 1.2.3, and remove code from
makepackage that cuts off last digit (and maybe output a warning during
build suggesting using less precise version).

I don't see any downside to it (aside from potential extra support code
upgrade). It will also keep support updates limited to the times when
they are actually needed (as opposed to the auto-updating solution).


---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]