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

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



On Thu, 2006-05-11 at 11:30 -0700, Chris Weyl wrote:
> On 5/11/06, Rex Dieter <rdieter math unl edu> wrote:
> > What is the purpose of this .pc file?  Most .pc files I've seen are -devel
> > related, but that doesn't mean *all* of them are.  They should be packaged
> > according to its purpose.
> 
> It "looks" like devel to me, but I'm no mono guy -- Brian? :)
> 
> [build zeus daap-sharp-0.3.3]$ cat daap-sharp.pc.in
> prefix= prefix@
> exec_prefix= exec_prefix@
> libdir= libdir@
> includedir= includedir@
> Libraries= libdir@/daap-sharp/daap-sharp.dll
> 
> 
> Name: daap-sharp
> Description: daap-sharp
> Version: @VERSION@
> Requires:
> Libs: -r:${Libraries}
> --EOF--
> 
> (Of course, that's the unretouched source file, but you get the idea.)
> 
> Even if it is for development, is it worth forcing it off into a
> -devel package for just one file?

Correct, this is used by pkconfig to pull in lib path when compiling.
The practice has been in Core & Extras for the most part (the only
exception I can think of is mono-devel) to include this in the main
package.

/B
-- 
Brian Pepple <bdpepple ameritech net>

gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B  CBDE 326A E936 810C C15E

Attachment: signature.asc
Description: This is a digitally signed message part


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