Am Dienstag, 28. August 2018 14:57 CEST, bill-auger <[email protected]> schrieb: > > On Tue, 28 Aug 2018 16:48:40 +0200 Hermann Meyer wrote: > > Using pkg-config means that it works on any system, even older ones, > > using pkg-config means that it works on any system that has pkg-config > installed - using pkgconf means that it works on any system that has > pkgconf installed.
No, using pkg-config means that the makefile will work on any system that uses pkg-config _and_ on any system that has a sane installation of pkgconf (i.e. one that symlinks pkg-config to pkgconf). - and either of pkg-config and pkgconf can be > installed on any system regardless of what the distro declares as the > "official" implementation > > > On Mon, 27 Aug 2018 21:23:47 +0200 Christopher Arndt wrote: > > Agree on both accounts. Just use 'pkg-config' like everybody else. > > building on what ralf wrote, the primary consideration should be only > what is best for the individual software projects - if both pkg-config > and pkgconf are binary-compatible then it probably makes absolutely no > difference to an upstream project - the only reason to take that > difference into consideration is if an upstream project > would were targeting one distro specifically or if you were a distro > packager (targeting one distro specifically) - then it would be more > convenient to use the implementation the disto has in it's repos The only reason to invoke pkgconf as pkgconf would be to target - a distro that used pkgconf but does _not_ install a symlink (which distro does this? (Arch/Fedora/CentOS/Debian all provide a symlink). - a project that would need to use features of pkgconf that are not available in pkg-config. Are there any? > otherwise, an upstream project that is not targeting one distro > specifically, should have no concern for this issue - it is the job of > packagers to make each program compile and run on their system - if > the 'foo' program can not be installed on one particular distro because > of some technical decision that distro made, that should be of no > concern to the upstream - but that is not the case here - if it were > absolutely necessary to install pkg-config on arch to get 'foo' working > then that can be done - and that is the concern of the arch packager > alone and no one else ??? So you would think it's ok if a makefile invokes ahardcoded gcc instead of cc even so the code compiles fine with clang or sun's cc? IIRC Fon's goal was to provide a rather generic makefile ... Cheers,RalfD _______________________________________________ Linux-audio-dev mailing list [email protected] https://lists.linuxaudio.org/listinfo/linux-audio-dev
