Porting to the Linux Standard Base 41
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."
Re:LSB is worthless (Score:3, Informative)
Not a flaw, basic sysadmin'ing... don't want to users fucking things up.
With the --prefix and --root switches for rpm, you can install software&libraries in your home directory.
Chapter 2. Using RPM to Install Packages [rpm.org]
Please someone provide a repository of statically linked open source software.
The downside with statically link executables is if there is a flaw(e.g. buffer overflow) with a library, you need to recompile&reinstall all the executables that have that library statically linked. Dynamically linked means just need to re-compile the offending library and restart the executable.
If you ever start to care for & feed a machine or three, you'll start to see there is a method to the madness.
Why use LSB? (Score:3, Informative)
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.
Re:LSB is worthless (Score:2, Informative)
I think LSB is great. For instance, people can write OpenGL-software and target lsb-graphics; instant portability.
And, most important of all, if you're ever to sell shrink-wrapped boxes with linux-software, you can attach an "LSB-compliant" sticker to it.