[opensuse-packaging] Packaging libraries that are intended to be static?
I'm building a package that includes this library: http://www.lonesock.net/soil.html This library is "meant to be used as a static library", so, I'm wondering if I should package it separately or not? I read the following, but still feel uncertain about what to do: http://en.opensuse.org/openSUSE:Shared_library_packaging_policy Thanks! ~D -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, 6 Dec 2011, David Lemke wrote:
I'm building a package that includes this library: http://www.lonesock.net/soil.html
This library is "meant to be used as a static library", so, I'm wondering if I should package it separately or not?
I read the following, but still feel uncertain about what to do: http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
Thanks!
Static libraries go into a -devel package. Richard. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wednesday 07 December 2011, Richard Guenther wrote:
On Tue, 6 Dec 2011, David Lemke wrote:
I'm building a package that includes this library: http://www.lonesock.net/soil.html
This library is "meant to be used as a static library", so, I'm wondering if I should package it separately or not?
I read the following, but still feel uncertain about what to do: http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
Thanks!
Static libraries go into a -devel package.
No, they should go into *-devel-static. http://en.opensuse.org/openSUSE:Packaging_guidelines#Static_Libraries cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wed, 7 Dec 2011, Ruediger Meier wrote:
On Wednesday 07 December 2011, Richard Guenther wrote:
On Tue, 6 Dec 2011, David Lemke wrote:
I'm building a package that includes this library: http://www.lonesock.net/soil.html
This library is "meant to be used as a static library", so, I'm wondering if I should package it separately or not?
I read the following, but still feel uncertain about what to do: http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
Thanks!
Static libraries go into a -devel package.
No, they should go into *-devel-static. http://en.opensuse.org/openSUSE:Packaging_guidelines#Static_Libraries
If there is no shared library? That would be excessive package number bloat. The -devel package would require the -devel-static package, which would never be useful to have installed on its own. Richard. -- Richard Guenther <rguenther@suse.de> SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
On Wed, 7 Dec 2011, Ruediger Meier wrote:
On Wednesday 07 December 2011, Richard Guenther wrote:
On Tue, 6 Dec 2011, David Lemke wrote:
I'm building a package that includes this library: http://www.lonesock.net/soil.html
This library is "meant to be used as a static library", so, I'm wondering if I should package it separately or not?
I read the following, but still feel uncertain about what to do: http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
Thanks!
Static libraries go into a -devel package.
No, they should go into *-devel-static. http://en.opensuse.org/openSUSE:Packaging_guidelines#Static_Libraries
If there is no shared library? That would be excessive package number bloat. The -devel package would require the -devel-static package, which would never be useful to have installed on its own. Read first, complain afterwards. The -devel package can ship static
On 12/07/2011 02:05 PM, Richard Guenther wrote: libs, but it has to provide a -devel-static package. Simple. -- Viele Grüße, Sascha
participants (4)
-
David Lemke -
Richard Guenther -
Ruediger Meier -
Sascha Peilicke