RE: Autopackage creation

> But how can I require atleast 1.2.5 without getting such error?

That's not an error, that's by design. I don't remember exact reason
behind this, but it was something security related.

You still can double click packages if you have support code installed,
so only terminal users will see that. (And those should be able to
figure it out :)).

BTW, if you want to require at least 1.2.5 (but not 1.2.4), you'll need
to patch autopackage a bit :)). 

In 
/usr/share/autopackage/stub.2.template
there is 
export AUTOPACKAGETERGET="%AutopackageTarget%"

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 :).

I do this for my packages, since I depend on several bugfixes that are
in later 1.2.x releases.


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