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:  yes that was a not a great analogy - my example was only meant
   to be general advice for any arbitrary dependency - it did not fit well for
   this case where that dependency is part of the tool-chain - indeed, you are
   correct that the very purpose of makefiles is to abstract over 
system-specifics
   in the tool-chain (and pkg-config itself is for abstracting system-specific
   library filenames) - if the two pkg-config binaries had different filenames
   then it would perhaps call for a new makefile variable like: $PKGCONF [...]
   

Content analysis details:   (5.5 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 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.5 AWL                    AWL: Adjusted score from AWL reputation of From: 
address


--- Begin Message ---
yes that was a not a great analogy - my example was only meant to be
general advice for any arbitrary dependency - it did not fit well for
this case where that dependency is part of the tool-chain - indeed,
you are correct that the very purpose of makefiles is to abstract
over system-specifics in the tool-chain (and pkg-config itself is for
abstracting system-specific library filenames) - if the two pkg-config
binaries had different filenames then it would perhaps call for a new
makefile variable like: $PKGCONF

in this particular case, as you noted, it is entirely a moot point
because those tools are binary-compatible; so the difference should be
of little or no concern to anyone - also, they are just auxiliary
build helper tools and not linked or sourced libraries, so even the
licenses are of no importance

--- End Message ---
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev

Reply via email to