To view parent comment, click here.
To read all comments associated with this story, please click here.
Except it doesn't mean anything, as the developer still needs to compile for all the architectures he wants to support. Being able to put all architectures in one only file contrasted to releasing multiple packages means shit if you still have to go through the compile process. If you are already supporting several architectures, then distributing a couple more packages doesn't make your life harder than it already is.
Keep that argument hammering on...
The packaging has still to be done, it doesn't matter if it's done in 5 separate packages or in a single FatELF, what's your point there?
If the packages doesn't package it, then it's not packaged, the format is irrelevant. It's not like FatELF is a robot that compiles for 20 architectures and then packages for you.





Member since:
2005-07-22
As commented already, the problem is that you need to compile first for different architectures and for different distributions. That means that you:
a) Have many computers with say Ubuntu x86, Ubuntu AMD64 and Ubuntu ARM, compile the source in the three and then what do you do with the resulting binaries to mix them into one fat binary? Too complicated.
b) Have one computer with cross compilers, then you compile the source with each compiler and then magically link all of them together to finally make dist in one single package.
c) Either a or b with single make $WHATEVER for every architecture.
In the end, the way it is now is simpler and works without doing anything. Distributing packages for different architectures is not a problem. Distribution sites usually check your browser ident to see which architecture to offer you by default. It works.