On Fri, Jun 1, 2018 at 11:55 AM, Daniel P. Berrangé
<berrange@xxxxxxxxxx> wrote:
Yeah if you add the gnutls-glib-networking.config file in the RPM,
that
defeats the point IMHO, as it'll never fallback to use @SYSTEM if this
file always exists with @GLIBNETWORKING defined in it.
The idea of the mechanism was that apps/libs build with @MYNAME,SYSTEM
priority but never define @MYNAME themselves, so it gives the local
sysadmin to customize the app/lib in isolation if they so wish, but
out of the box still respects @SYSTEM.
If @SYSTEM is changed as proposed, then glib-networking must not
out-of-the-box respect @SYSTEM, because it needs to out-of-the-box
work. :) So I guess we should just not use @SYSTEM then, yes?
I wonder what Tomas intends here.
Michael
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/UXJ6VAWQPN35HUHUCES4DKOQL32LWI5Y/
