Linked by David Adams on Mon 4th Aug 2008 19:03 UTC
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 325603
To read all comments associated with this story, please click here.
Hopefully in the future instead of releasing software for Redhat or Novell, they give requirements as "requires a distro of LSB 4.1 or better". That will be the day when apps will work across distros without having to worry about incompatibilities.
I don't, honestly, ever see that happening. At least not in the distant future.
Companies that produce commercial packages for linux that specify RHEL or SLES will be able to engage Red Hat or Novell for support if any issues arise with compatibility. That's the whole point behind targeting those distros.
Applications might be produced to be LSB x.y compliant, but few commercial ISVs will stake their support on generic distros. Though at least having LSB compliant packages produced will be a start, it will just leave the customer to fend for themselves on support issues if they're not using a pre-approved distro. Red Hat, Novell, Gentoo, Arch and Ubuntu might all provide library foo.bar, but that doesn't ensure it will operate identically in each environment. THAT is the support nightmare ISVs will try to avoid.
Still, I think standardization is a good thing, since it points in the right direction. But things will certainly not change overnight, even with a standard in place.
Member since:
2005-07-13
I don't, honestly, ever see that happening. At least not in the distant future.
Companies that produce commercial packages for linux that specify RHEL or SLES will be able to engage Red Hat or Novell for support if any issues arise with compatibility. That's the whole point behind targeting those distros.
Applications might be produced to be LSB x.y compliant, but few commercial ISVs will stake their support on generic distros. Though at least having LSB compliant packages produced will be a start, it will just leave the customer to fend for themselves on support issues if they're not using a pre-approved distro. Red Hat, Novell, Gentoo, Arch and Ubuntu might all provide library foo.bar, but that doesn't ensure it will operate identically in each environment. THAT is the support nightmare ISVs will try to avoid.
Still, I think standardization is a good thing, since it points in the right direction. But things will certainly not change overnight, even with a standard in place.