Mark Martin wrote: > Alan Coopersmith wrote: >> Mark Martin wrote: >> >>> Well for good or bad, I've noticed .pc files before, questioned them, >>> and the teams have simply removed them. >> >> You sure you're not confusing those with .la files? libtool-generated >> .la files should not be delivered, but .pc files are used by pkg-config >> so that packages with dependencies can determine what flags to use for >> building and linking. >> >> > Nah, I meant ".pc" files. I should correct myself, though. They > weren't removed -- instead the stability on those particular artifacts > went from Uncommitted -> Cons. Private. > http://arc.opensolaris.org/caselog/LSARC/2008/782/mail
The name of the .pc file should have the same stability level as the library - maybe higher but certainly not less. The content of the file should be Volatile because it can (and will in some cases) change from invocation to invocation. It is Volatile rather than "Not an Interface" because it is intended to be consumed programatically, the format is fixed by pkg-config(1) but the actual output for any given .pc file varies depending on versions and what arguments were passed to pkg-config(1). As for versioning the version information is held inside the .pc file. -- Darren J Moffat
