64-bit
Justin Karneges <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello all, We use Autopackage at Barracuda Networks for distributing our IM Client for Linux. Recently we ran into a problem where users on 64-bit Linux platforms are unable to complete the install process. I'd have probably written this off as a minor detail, since Linux is a fringe platform in the first place, and surely 64-bit Linux is even more fringe --- except that it turns out we have an entire internal department using 64-bit Linux. This ended up being a very embarrassing situation when it came time to deploy our own software. I did some googling, as well as checked out the autopackage mailing list archives, forum, and IRC logs to get myself up to speed. From what I gather, there has not been much consideration for 64-bit Linux. Since autopackage appears to be the best tool for the job of installing third-party Linux apps, I'm willing to assist with making it work. I'm really hoping I don't have to fallback to making rpms/debs for the 64-bit platforms. Questions: 1) Is it possible to make a 64-bit-only version of a .package? Then we could offer two package files, and users would just need to pick the right one. The IRC log seemed to hint that this may be possible by bundling the autopackage files (this seems to be needed anyway to avoid the 404 error during install). 2) Is it possible to make a 32-bit package that works on both 32-bit or 64-bit platforms, with very minimal user instructions? Something like "install the 32bit compat libs, then run our 32-bit application package" would be nice. I saw this idea mentioned during my searches, but it wasn't stated confidently (I get the impression that none of the AP devs have 64-bit systems...). 3) Is there a long-term goal to allow a single package to provide both 32-bit and 64-bit versions? This would be the most ideal, giving an effect similar to Mac "universal" binaries. 4) Is Autopackage dead? (maybe stupid question, but I was reading some Linux.com article about how autopackage doesn't get worked on, and that worries me). If I must go somewhere else for my solution, I hope you'll be honest and tell me that's what I should do. That said, if it is simply a matter of autopackage being incomplete (e.g. it is the right way if only it were actually written), then I may be able to help complete it. Thanks, -Justin --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]