[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: mono / ".pc files in -devel packges" guideline



Michael Schwendt wrote:

> On Fri, 12 May 2006 08:59:29 -0500, Tom 'spot' Callaway wrote:
> 
>> On Thu, 2006-05-11 at 15:08 -0400, Brian Pepple wrote:
>> 
>> > > Even if it is for development, is it worth forcing it off into a
>> > > -devel package for just one file?
>> 
>> If the .pc file is the ONLY file that would qualify for -devel (aka, no
>> headers, no static libs, nothing to develop a program against), then
>> there is no reason to force a -devel subpackage just for it.
> 
> There is one good reason: The .pc file contains dependencies on other .pc
> files, which are located in -devel packages. In this case, you would need
> a dependency ("Requires") from your non-devel package to -devel packages.
> Without that dependency, your package would break the pkgconfig dependency
> chain and several pkgconfig query commands.
> 
> To keep development files in -devel packages is the only clean solution.

Keep in mind recent rpm versions (in development) automatically include all
the Provides/Requires from .pc files as well.

-- Rrex 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]