Porting to the Linux Standard Base
An anonymous reader writes "If an application conforms to the Linux Standard Base (LSB), and a flavor of Linux is LSB compliant, the application is guaranteed to run. This tutorial, written by Martin Streicher, Editor in Chief of Linux Magazine, ensures that your code runs reliably on as many Linux flavors as possible. It shows you how to port your apps to the Linux Standard Base, then takes you through the LSB test tools to verify conformance."
and was just an attempt by redhat to push the subpar RPM package format. If they were serious about a somewhat standard linux, they would have started with debian.
"If they were serious about a somewhat standard linux, they would have started with debian."
1-LSB is more than just RPM.
2-There's nothing wrong with RPM. Just the people who use it.
It' looks like it only applies to package formats. Am I wrong?
I would really love to see this implemented by everyone!!! http://en.wikipedia.org/wiki/Filesystem_Hierarchy_ Standard
"Anyone have a "public" version of this doc?"
Building Applications with the Linux Standard Base
GNU Autoconf and Automake, when used properly, allow for packages to build on any almost-POSIX-compliant system {I won't say fully-POSIX-compliant because AFAIK nothing is fully-POSIX-compliant}. That's Linux, BSD, AIX, Solaris, Apple; and even Windows NT4 / 2000 / XP. Windows 98 / Me with Cygwin.
LSB is merely a way to push closed source software onto Linux through the back door. We have language specifications and POSIX to ensure source compatibility. Binary compatibility is not necessary, and there are valid arguments suggesting it is not even desirable.
Je fume. Tu fumes. Nous fûmes!
There are three distributions listed that conform to LSB3.0: SUSE, RedHat, and Asianux. Why should I write for LSB?
FTFT (from the...tutorial): LSB has binary compatibility standards, so I can compile once and run anywhere. But if the application is GPL and nontrivial, it shouldn't be that hard to get it into the package repositories in question. Otherwise, it's probably in a scripting language, so the end user doesn't have to build or install it anyway.
This is really only important for commercial Linux software.
The point of dynamic libs is not just the memory savings, both RAM and disk, but the bug fixing. You fix a bug in a lib, all the linked apps get it fixed by definition. Static apps require the vendor to relink and rerelease the apps.
There is also a small slowdown with dynamic apps, load and runtime, but that has never bothered me.
Infuriate left and right
...but don't feel bad, so do most people on this forum
_ Standard
It' looks like it only applies to package formats. Am I wrong?
Yes, you are almost completely wrong. LSB applies to much more than package file formatting. LSB distributions have a common set of libraries and such, so that every single LSB package has the exact same set of dependencies--those defined by the spec. There is even a package NAMING convention that must be followed to ensure there are no package naming conflicts.
I would really love to see this implemented by everyone!!! http://en.wikipedia.org/wiki/Filesystem_Hierarchy
Then you'd really love to see LEB implemeted by everyone too, becasue the FHS is one aspect of the LSB.