Posted by: Administrator
on October 11, 2005 09:10 PM
I need some comments on this, tell me how ya'll think this would work:
*Basically, there is a set standard that defines what libraries come in a full desktop distro. This covers the GNU, X, Gnome & KDE and other libraries which are considered standard and so on. Maybe SDL...
*A program which requires a library not featured in the standard would simply statically link it into the program.
The goal of the standard is to ensure common libraries so that things usually aren't redundantly statically linked (But this may happen sometimes) but at the same time lay out that certain libraries (Who in the world would just happen to have "pan-tools" unless they installed it manually?) won't be availible and they ought to be compiled into the app.
OR, maybe do something like, the 'RPM' package has the non-standard libraries in it and installs them as dynamically linked shared libraries, this way if someone installs two programs which have common shared libraries, they both get installed.
I'm skipping over details like tracking versions, but that would be in the system too.
The result would basically be that if one has a distro built against the standard, than one only needs to have RPMs (or whatever) built against it as well, not built against the distro specifically, and they would run... Period. With no DLL problems or elaborate networks or anything.
It's a simpler solution to an even simpler problem, I think. Distros and put whatever they want on top of the standard, all it'd be is an assurance that a set of shared libraries is going to be there and under a certain naming scheme.
LSB does this sorta but it doesn't nearly cover enough to define a whole desktop platform, I just looked at LSB 3.0 and it only covers up to some X and OpenGL stuff. Most programs require a lot more than is defined in the LSB specification.
Learn about Linux
Download Linux
Get Linux help
My Idea
Posted by: Administrator on October 11, 2005 09:10 PM*Basically, there is a set standard that defines what libraries come in a full desktop distro. This covers the GNU, X, Gnome & KDE and other libraries which are considered standard and so on. Maybe SDL...
*A program which requires a library not featured in the standard would simply statically link it into the program.
The goal of the standard is to ensure common libraries so that things usually aren't redundantly statically linked (But this may happen sometimes) but at the same time lay out that certain libraries (Who in the world would just happen to have "pan-tools" unless they installed it manually?) won't be availible and they ought to be compiled into the app.
OR, maybe do something like, the 'RPM' package has the non-standard libraries in it and installs them as dynamically linked shared libraries, this way if someone installs two programs which have common shared libraries, they both get installed.
I'm skipping over details like tracking versions, but that would be in the system too.
The result would basically be that if one has a distro built against the standard, than one only needs to have RPMs (or whatever) built against it as well, not built against the distro specifically, and they would run... Period. With no DLL problems or elaborate networks or anything.
It's a simpler solution to an even simpler problem, I think. Distros and put whatever they want on top of the standard, all it'd be is an assurance that a set of shared libraries is going to be there and under a certain naming scheme.
LSB does this sorta but it doesn't nearly cover enough to define a whole desktop platform, I just looked at LSB 3.0 and it only covers up to some X and OpenGL stuff. Most programs require a lot more than is defined in the LSB specification.
Comments? Suggestions?
#