A new version of the Autopackage cross-distribution packaging system for Linux has been released. The most important enhancement in the new 1.2 version is the improved C++ support, making it possible to create a package that will install on systems with different C++ ABI versions (gcc 3.2 or gcc 3.4). Also, first steps to integrate Autopackage with native package managers have been done: now it is possible to uninstall an RPM package conflicting with the autopackage that is being installed. There are also many other GUI and backend improvements.
So easy and gets the deps for you, best way to get the latest XaraXL as well.
Nah, the best way to get XaraLX is to: yum install XaraLX in FC5 🙂
…or apt-get install xaralx in Etch
Not everybody uses Etch. There are many, many, many users who use other distributions which don’t have XaraLX in their repository, or don’t have enough manpower to package XaraLX too. That is one of the reasons why Autopackage exists.
don’t have enough manpower to package XaraLX
Find a distro that has better support? If they lack the manpower to add something like that I wouldn’t want to rely on them for security updates.
Edited 2006-10-20 02:52
“Find a distro that has better support?”
It is not up to us to judge whether the user is using the right distro. The user may have a legitimate reason to use that specific distro even though it lacks the man power to package a lot of things. The user should not have to suffer from that decision, software installation should be easy regardless of which distribution they use (within reasonable limits of course; I don’t expect new software to run on RedHat 1.0 for instance).
This is good news for everyone using Linux.
Now we need more people making autopackages so we can stop relying on distros to provide updates to packages.
Before the flaming starts, I’d like to point out some common misunderstandings and questions that typically arise from people unfamiliar with Autopackage.
1) Autopackage is not meant to replace your native package manager (rpm/dep/etc.)
2) It’s probably not a good idea to build a distro completely based upon Autopackage. It’s just not designed for that.
3) The autopackage/native package integration is still a work in progress and not 100% reliable yet.
See our faq for more answers: http://www.autopackage.org/faq.html
/Isak
Is ok but yum rullez FC5