Re: Autopackage creation

On Wed, Jun 4, 2008 at 5:53 PM, Eugene Zolenko
<EugeneZolenko-XYgkjQFSZqy1Z/[email protected]> wrote:
>> But how can I require atleast 1.2.5 without getting such error?
>
> You'll need to hardcode it to be 1.2.5, otherwise makepackage will
> replace it with 1.2, and any 1.2 will do, as per CompareVersions()
> specification.
>
> *hides behind cover before autopackage devs hit him with a brick :).

Throws a big brick towards eugene!  ;-)

Seriously though, it is exactly the reason you specified in another
reply, that all 1.2.x releases are compatible and there's no reason to
force an upgrade if the user already has an 1.2 version installed. In
theory.

We've all seen that practice may differ from theory though :(

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.

-Isak

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