Posted Mar 31, 2005 8:29 UTC (Thu) by boudewijn
In reply to: Autopackage 1.0
Parent article: Autopackage 1.0
First, the habit to download applications from other places than the
distribution-sanctioned ones is also widespread in Linux, so there's no
need to be snotty about it. There are countless website hosted by
sourceforges that offer a range of rpms and debs...
And it's not just proprietory software vendors who don't like to create an
rpm for every distribution under the sun; Autopackage also solved my
problem very neatly. I'm the maintainer of Krita and I wanted to make
available a binary of Krita for people to test. Telling people to use a
source package was no option, because the source package of Krita includes
KOffice, and installing a KOffice cvs might hurt their existing
installation of their productivity tools.
So I used apbuild to build a binary, with ImageMagick and lcms statically
linked and made that binary available from my homepage. For a lot of
people it just worked -- I've had success on SuSE 9.1 and 9.2, Ubuntu
Warty, Fedora Core 3 and Peanut Linux. I didn't go the whole hog of
creating a complete autopackage, mainly because I didn't have the time to
figure it out, but for the bimonthly releases of Krita we are planning
after the KOffice 1.4 release in June 14 I am certainly considering
autopackages. I simply don't want to have to create debs and rpms and what
not for all the distributions out there.
to post comments)