RE: Autopackage @ LinuxTag in Berlin

From: Isak Savo [mailto:[email protected]]=20
>> Its goal is to make it possible to create only one package for all
>> kinds of Linux distribution to make software distribution easy for
>> both developers and users. For example an Autopackage only needs one
>> package for 32 bit and 64 bit machines. Furthermore binary
>> compatibility issues are solved using Apbuild, a wrapper around GCC
>> which makes it possible to solve bogus dependencies and different
>> versions of glibc.

>I agree with Mike here, "bogus deps" won't be understood. I suggest
>staying at a higher level, perhaps:
>"To help developers create binaries that works across multiple
>distribution, autopackage includes a tool called APBuild that works
>around many portability issues that occur during normal compilation"

>You may even wanna leave out the "during compilation" part

I think if you leave out too much people start to wonder what problem exact=
ly it solves. Because incompatibility during compilation is what it is for.=
 People who don't distribute binary packages don't have the problem. People=
 who do -- know what compilation is and might be doing something already to=
 solve it. We actually used old machine with FC 3 on it to build binary com=
patible packages before we switched to APBuild. (Also might want to say it =
is for C and C++, since that about all it does, right?)

Don't be too generic - overtly generic text doesn't say anything :).


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