pkg-config2

[Daniel Stone]

On Sat, Jan 22, 2005 at 10:53:23PM -0500, Maks Orlovich wrote:
> On Saturday 22 January 2005 10:46 pm, Daniel Stone wrote:
> > On Sat, Jan 22, 2005 at 09:59:11PM -0500, Ian Reinhart Geiser wrote:
> > > On Saturday 22 January 2005 20:20, Daniel Stone wrote:
> > > > Not being funny or anything, but what development is there really to
> > > > do? Some stuff is stagnant just because there isn't really anything to
> > > > do, bar cleaning up an M4 warning.
> > >
> > > Well currently there is duplication in applications like kde-config
> >
> > I strongly believe that kde-config should not exist, and that it should be
> > a function of pkg-config.
> 
> Probably because you don't know what it does. Actually, there is no overlap in 
> functionality.

Looking over kde-config, it does exactly what I thought it does, and I see a
massive overlap in functionality.

You can extract arbitrary data from pkg-config: you are not limited to cflags.
If you define kdeconfigpath, et al, to be a standard for all KDE apps, then you
can all use the standard pkg-config implementation, and have everyone still
using the same frontend.  You could even define -prefix or -noprefix to get it
with or without ${prefix}, if you wanted, e.g.:
	kdeconfigpath: ${prefix}/share/applications
	kdeconfigpath-noprefix: share/applications

Daniel, looking and seeing no functionality that *doesn't* overlap
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/xdg/attachments/20050123/fd2e2d75/attachment.pgp