On Wed, 2017-01-04 at 09:20 +0100, Jan Kurik wrote: > = System Wide Change: pkgconf as system pkg-config implementation = > https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_i > mplementation > > Change owner(s): > * Igor Gnatenko <ignatenkobrain AT fedoraproject DOT org> > * Neal Gompa <ngompa13 AT gmail DOT com> > > This change switches Fedora's system-wide/default pkg-config > implementation to pkgconf, a new implementation of pkg-config that > provides better support for handling .pc files and a stable library > ABI/API for integrating into applications. I think it would be really helpful to know a bit more background - who are the people developing pkgconf, how did the project start? Has there been discussion with the current pkg-config maintainers about what they think of this project and whether they would want to retire pkg-config in favor of this project? And why is an incompatible 'pkgconf' command line needed in addition to the pkg-config wrapper? If the pkgconf project was the official version of pkg-config and they could evolve the 'pkg-config' command line would that be sufficient? Having two commands sounds like it will make documentation about anything related to .pc files much more confusing. (And pkg-config vs. /usr/lib/pkgconfig was already confusing...) I don't see a problem with pkg-config being rewritten, but I do see a problem if there's a fork without a clear direction that is likely to be followed by all distributions. There has to be a single definition of what goes in a .pc file and what the interface is, and what happens when you run pkg-config, or use PKG_CHECK_MODULES in a configure.ac file. - Owen _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
