[opensuse-packaging] Shared Library Packaging Policy (was: [opensuse-factory] Meeting Minutes Dist Meeting 2007-05-10)
![](https://seccdn.libravatar.org/avatar/52bd4d52d386482c424edc0790c28ec9.jpg?s=120&d=mm&r=g)
Andreas Jaeger wrote:
* Shared library policy see: http://en.opensuse.org/Shared_Library_Packaging_Policy
If nobody raises objections, we'll move forward with it and add it to the packagers manual.
Note: This is not enforced for existing packages. It should be done for major updates and must be done for new package submissions.
AI: everybody to read and comment on opensuse-packaging mailing list.
Hi, I miss somthing in the new package conventions. We should start to avoid -rpath. Packages should be built without -rpath and if they need a special path, a file in /etc/ld.so.conf.d/ should be created. Google: "rpath is evil" The solution to get the libraries working without rpath is the use of ldconfig. Suppose you have the library /usr/lib/foo/foo.so.0. Then simply create a file /etc/ld.so.conf.d/foo with the path (/usr/lib/foo) as the content. Cheers, -- andreas -- http://www.cynapses.org/ - cybernetic synapses
![](https://seccdn.libravatar.org/avatar/835a9492d596a5f4a8eba92c90ac373b.jpg?s=120&d=mm&r=g)
On Mon, 14 May 2007, Andreas Schneider wrote:
Andreas Jaeger wrote:
* Shared library policy see: http://en.opensuse.org/Shared_Library_Packaging_Policy
If nobody raises objections, we'll move forward with it and add it to the packagers manual.
Note: This is not enforced for existing packages. It should be done for major updates and must be done for new package submissions.
AI: everybody to read and comment on opensuse-packaging mailing list.
Hi,
I miss somthing in the new package conventions. We should start to avoid -rpath. Packages should be built without -rpath and if they need a special path, a file in /etc/ld.so.conf.d/ should be created.
Google: "rpath is evil"
The solution to get the libraries working without rpath is the use of ldconfig. Suppose you have the library /usr/lib/foo/foo.so.0. Then simply create a file /etc/ld.so.conf.d/foo with the path (/usr/lib/foo) as the content.
I agree. Still for programs which come with their own shared libraries installed in /usr/lib/$program/ rpath is a reasonable setup - this also avoids polluting the global "soname namespace" for purely internal shlibs. Richard. -- Richard Guenther <rguenther@suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/a769262fe9a53e49df65ec5fbf8f5de9.jpg?s=120&d=mm&r=g)
On Monday, 14. May 2007, Andreas Schneider wrote:
I miss somthing in the new package conventions. We should start to avoid -rpath. Packages should be built without -rpath and if they need a special path, a file in /etc/ld.so.conf.d/ should be created.
We're stripping rpath for all paths that are in /etc/ld.so.conf internally and also try to reject obviously stupid ones. So this is just about an enhancement request against the opensuse buildservice FYI. Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Andreas Schneider
-
Dirk Mueller
-
Richard Guenther