| |||||||||||||
SELF: Anatomy of an (alleged) failureSELF: Anatomy of an (alleged) failurePosted Jun 24, 2010 16:03 UTC (Thu) by error27 (subscriber, #8346)Parent article: SELF: Anatomy of an (alleged) failure
In the end aren't you still going to use rpm to put your fatelf binaries on the filesystem in the right place? Could the rpm format be extended to include more than one arch? You'd put two binaries into the same rpm and only install the right one.
The thing about it is that if you don't add a feature, you can change your mind later and add it. But if you do add a feature, you can't remove it. Looking through this list, in retrospect most of the decisions were the correct ones.
The sad bit is if you end up pissing off a developer. Especially it's sad that Con was upset.
(Log in to post comments)
SELF: Anatomy of an (alleged) failure Posted Jun 24, 2010 22:01 UTC (Thu) by MisterIO (guest, #36192) [Link]
IMO Con reacted in a somewhat childish way, but I can nonetheless see some truth in this post:
http://lkml.org/lkml/2007/8/1/7
SELF: Anatomy of an (alleged) failure Posted Jun 25, 2010 9:54 UTC (Fri) by paulj (subscriber, #341) [Link]
That's pretty much how IRIX pkg worked, to deal with the various ABIs (o32, n32 and 64bit).
SELF: Anatomy of an (alleged) failure Posted Jun 25, 2010 13:59 UTC (Fri) by vonbrand (subscriber, #4458) [Link] The solution adopted is not a fat RPM containing several versions, but separate (but coordinated) RPMs for the different architectures. Look at current Fedora repositories for x86_64, they have packages for 32 and 64 bits. If I want to install one or the other or both, I can do so. No need for 32-bit people do get the for them useless 64-bit versions, no need for pure 64-bit systems to be burdened with 32 bit stuff.
SELF: Anatomy of an (alleged) failure Posted Jun 26, 2010 18:13 UTC (Sat) by tzafrir (subscriber, #11501) [Link]
So which package includes /usr/bin/hello ? The i386 one? The amd64 one? The i686-with-uclibc one? The armel (v4) one?
SELF: Anatomy of an (alleged) failure Posted Jun 27, 2010 11:59 UTC (Sun) by tialaramex (subscriber, #21167) [Link]
All of them, the package management software is aware of your preferred architecture and will install that package. Packages which provide dependencies (e.g. a library) can be multiply installed, so that both the 32-bit and 64-bit library are installed, each from its own package.
This stuff has all been working and in everyday use for some time.
|
|||||||||||||