Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Autopackage support (binaries for Linux)
08-11-2005, 12:01 PM,
#22
Autopackage support (binaries for Linux)
Your system is not a valid example. You run a legacy system. The source code is available for the tiny minority of users like yourself.The premise of autopackage is that you don't need to provide apt/rpm support, just autopackage. For something like VDrift that runs as an end-user app (a leaf application, if you will) and not a library, not being 'integrated' with the local package manager is not an issue, you can just download updates as and when you need them.Also apt/rpm is not a 2-prong solution. A .deb built for Ubuntu will most likely not install on a Debian system, and a .deb built for Debian will not always install on Ubuntu. The scenario is even worse with RPM, and I endured absolute hell a few years back trying to install things on Mandrake - basically anything other than an official Mandrake .rpm would not work and even the official ones would not always work.Autopackage merely attempts to remove all the above pain and reduce the workload for developers (be they contributory or long term).Maybe providing a well-built rpm or deb might be desirable - Inkscape do it in addition to providing an autopackage - but the best way to reach the most users with the least effort is definitely via Autopackage. I just installed the Inkscape autopackage on my system and can not stress enough how effortless it was.
Reply


Messages In This Thread
Autopackage support (binaries for Linux) - by charlieg - 08-11-2005, 12:01 PM
[No subject] - by thelusiv - 06-05-2006, 10:17 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)