Re:Why Desktop Linux (Still) Sucks. And What We Can Do To Fi...
by thingie on Tuesday April 27, 2010 @02:30AM
(#1297418)
Yes, suse build service is a very nice tool and much more interesting than a single package format, which wouldn't help much. And if the dream is to provide just a single binary package for any distro in the world, it won't work anyway. Well, maybe in theory, but if you mean it seriously, you need to compile and link against exactly the same binaries that the target system use. (Or static linking. Or just believe it will work. But serious commercial vendor who wants to provide a real user support cannot.) Which would mean that every Linux system would have to use the same binaries, which is, hm, nonsense.
Re:Why Desktop Linux (Still) Sucks. And What We Can Do To Fi...
by sophacles on Tuesday April 27, 2010 @01:52AM
(#1297344)
Meh, from a source point of view, once I have a debian/ directory, with a properly set up rules file, building becomes trivial. Then it is matter of generating a package per-distro/version with the right environment. This could be very well done in an automated manner and a few vms.
Re:Why Desktop Linux (Still) Sucks. And What We Can Do To Fi...
by codavid on Tuesday April 27, 2010 @02:20AM
(#1297401)
Which is exactly what the build service gives you...
Re:Why Desktop Linux (Still) Sucks. And What We Can Do To Fi...
by sophacles on Tuesday April 27, 2010 @10:58AM
(#1298398)
My bad, I was under the impression that it was an RPM only thing.
Re:Why Desktop Linux (Still) Sucks. And What We Can Do To Fi...
by krschultz on Tuesday April 27, 2010 @12:47PM
(#1298791)
I hear what you are saying, but we can reduce the differences between build systems while still using different targets.
I do a lot of work with OpenEmbedded, every distro image you create is for a different hardware platform, using different libraries, different tools, etc. But it is a unified build system. So I can say use this version of glibc and spit out the files in that folder, and with very minor tweaks I can use a completely different version of glibc and a different file structure for another image. If we had a unified dependency/build system across distros, we could have completely different contents while having relatively straightforward customization because if you knew one system, you'd know them all.
Once you standardize on what makes packaging difficult across distro, you basically end up with the same system. I think systems like the build service from Suse, etc... are much more useful than wishful thinking on packaging format.