Re: Binary .package Why?

2008/1/18, Alex Lobanovsky <[email protected]>:
> Hello ALL,
>
> first of all, thank you for the product and all great work you've done!
> Impressive!
>
> I'm playing now with autopackage to see if it fits my needs. The first very
> dummy apspec I created, targets very simple goal - to check if Python of
> version 2.5.x is installed on a target platform. I followed all the
> instructions and finally I got my .package file. But it has binary format
> and my test target refuses to run it! Why is that so? All the .package files
> I downloaded from aoutopackage.org are just ASCII bash scripts. I'd wanted
> to have bash script as well. Do I miss something?

Everything created by "makepackage" are bash scripts, so I don't
understand what happened to you.

By the way, what do you mean by "binary"? A major part of a .package
*is* binary data (the actual data payload), but the top part of the
file is bash code.

Can you tell us how you created the package, what specific error
messages you get when you try to install it and so on?

-Isak

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