Linked by David Adams on Mon 4th Aug 2008 19:03 UTC
Linux Not all Linux distributions are made with the same components, which can make it difficult for software developers to write applications for multiple Linux distributions. That's where the Linux Standards Base (LSB) comes into play. For years the LSB has not quite lived up to its full potential. That could all change with the upcoming LSB 4.0 release.
Permalink for comment 325602
To read all comments associated with this story, please click here.
elsewhere
Member since:
2005-07-13

If I remember correctly, LSB used to specify RPM to be the standard tool for packages. I hope they've fixed that by now. Practically every distribution has its own package manager; there's no reason for any of them to switch to RPM.


This is a tired argument, but rpm the package-format was specified, not rpm the package installer. Even rpm-based distros don't rely exclusively on rpm as a package installation method.

And before anyone mentions it, .deb is a proprietary package format for Debian-based distributions. It doesn't matter if there are 700 different Debian-derived distributions on the planet.

And before anyone mentions it, proprietary doesn't have to mean closed or non-free. The point is .deb is designed for Debian distros. Period.

.rpm is, at least, distro agnostic.

Has nothing to do with package managers. You can use Smart with almost anything for instance, doesn't matter.

Reply Parent Bookmark Score: 2