sven.vermeulen at rug.ac.be
Sun Apr 7 03:32:16 PDT 2002
After a quick look through the mailinglist archives I got the idea that some
were thinking about another packaging format (i.e. not RPM, but RPM-alike).
Are there any persons working on that or has this idea been dropped?
I also have a question about the dependencies. A package must depend on lsb,
and lsb only. So any library needed for a program to run that is not part of
a lsb-compliant system must be inserted into the package. The chances are
great that more than one application needs a certain library. How will the
packaging format deal with this?
F.i. package lsb-A provides a program called foo and library bar.so.0 and a
package lsb-B provides a programm called bleh and library bar.so.0. A
sysadmin needs to install both packages. First he installs lsb-A and then he
wants to install lsb-B. The system (well, the packaging binary) will see that
bar.so.0 is already on the system. What should it do? Raise an errormessage
explaining that the two packages conflict? Register that bar.so.0 is now
"installed" by both packages?
A host is a host,
From coast to coast
And nobody talks to a host that's close,
Unless the host that isn't close
Is busy, hung, or dead.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 232 bytes
Desc: not available
Url : http://lists.linux-foundation.org/pipermail/lsb-discuss/attachments/20020407/e50013c3/attachment.pgp
More information about the lsb-discuss