Spam detection software, running on the system "mail1.linuxaudio.cyso.net",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview: 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
- and either of pkg-config and pkgconf can be installed on any system
regardless
of what the distro declares as the "official" implementation [...]
Content analysis details: (5.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 BAD_ENC_HEADER Message has bad MIME encoding in the header
2.5 RCVD_IN_SORBS_HTTP RBL: SORBS: sender is open HTTP proxy server
[75.138.187.221 listed in dnsbl.sorbs.net]
2.4 RCVD_IN_SORBS_SOCKS RBL: SORBS: sender is open SOCKS proxy server
1.1 DATE_IN_PAST_03_06 Date: is 3 to 6 hours before Received: date
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's
domain
-0.5 AWL AWL: Adjusted score from AWL reputation of From:
address
--- Begin Message ---
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 - 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
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
--- End Message ---
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
