Comments on A New Approach to the LSB (part 2) News and views from the Licquia family2005-12-13T20:59:16Zhttps://www.licquia.org/archives/2005/06/16/a-new-approach-to-the-lsb-part-2/feed/WordPress
By: Nathanael Nerode Nathanael Nerodehttp://www.licquia.org/?p=102#comment-57042005-12-13T20:59:16Z2005-12-13T20:59:16ZGood ideas all. When can we get this into Debian? 😛
]]>
By: Ian Murdock’s Weblog » When is a fork not a fork? Ian Murdock’s Weblog » When is a fork not a fork?http://ianmurdock.com/?p=273http://www.licquia.org/?p=102#comment-51862005-09-15T17:46:32Z2005-09-15T17:46:32Z[…] Of the remaining 29 packages, 4 are the LSB 3.0 compatibility environment, which adds the necessary packages to achieve LSB 3.0 compliance in such a way that the sarge glibc and pam packages don’t need to be modified (these packages needed modifications to achieve LSB 3.0 compliance—see Jeff Licquia’s weblog for details here and here). The only applications that use the LSB compatibility environment are LSB applications—the default application environment is the standard Debian environment. […]
]]>
By: Matt Wilson Matt Wilsonhttp://www.licquia.org/?p=102#comment-46832005-06-16T21:03:35Z2005-06-16T21:03:35ZWe added the requirement for LSB applications to use ld-lsb.so.1 for PT_INTERP so that a distro can replace ld-lsb.so.1 with a dynamic linker that pulls in LSB-compliant libraries. In other words, this is exactly why it’s required.
]]>
By: spacehunt » Making Debian LSB compliant spacehunt » Making Debian LSB complianthttp://spacehunt.info/?p=5http://www.licquia.org/?p=102#comment-46822005-06-16T18:31:56Z2005-06-16T18:31:56Z[…] SB compliant Filed under: Debian — spacehunt @ 2:30 am Jeff Licquia’s proposal for making Debian LSB compliant is the same one that weR […]
]]>