[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-packaging
Subject:    Re: [opensuse-packaging] advice on packaging a static library
From:       Richard Guenther <rguenther () suse ! de>
Date:       2012-02-28 9:09:31
Message-ID: alpine.LNX.2.00.1202281008500.18230 () zhemvz ! fhfr ! qr
[Download RAW message or body]

On Mon, 27 Feb 2012, Greg Freemyer wrote:

> All,
> 
> I'm trying to package guymager and libguytools.  They work together
> and guymager buildrequires the library.
> 
> libguytools is really just some /usr/include/libguytools/*.h files and
> a static library.  That seems wrong to me, but its the way they have
> it broke up at sourceforge.
> 
> I've got a package for libguytools in my home project.
> (home:gregfreemyer:Tools-for-forensic-boot-cd > libguytools )
> 
> Right now, the main libguytools package is empty and I've got 2 sub-packages:
> 
> %files -n %{name}-devel
> %defattr(-,root,root,-)
> %{_includedir}/libguytools2/
> 
> %files -n %{name}-devel-static
> %defattr(-,root,root,-)
> %{_libdir}/libguytools.a
> 
> 
> Is this approach acceptable?
> 
> I seriously doubt there is another user of the libguytools library
> floating around anywhere.  Should I just combine this package with the
> guymager package somehow?
> 
> I don't yet have a good guymager package at all.  I'm starting with the library.

If there is no shared library it does not make sense to package the
static lib separately, so I'd say it should go into the -devel package.

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
-- 
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org


[prev in list] [next in list] [prev in thread] [next in thread]