| Newsgroups |
gmane.linux.lfs.beyond.devel |
| Message-ID |
<[email protected]> |
On Wed, 2025-04-30 at 23:49 -0500, Douglas R. Reno wrote:
> On 4/30/25 11:08 PM, Xi Ruoyao ([email protected] via blfs-dev
> Mailing
> List) wrote:
> > On Wed, 2025-04-30 at 22:51 -0500, Douglas R. Reno wrote:
> > > On 4/30/25 10:50 PM, Xi Ruoyao ([email protected] via blfs-dev
> > > Mailing
> > > List) wrote:
> > > > On Thu, 2025-05-01 at 03:47 +0000, Git Owner wrote:
> > > > > This is an automated email from the git hooks/post-receive
> > > > > script.
> > > > >
> > > > > git pushed a commit to branch trunk
> > > > > in repository blfs.
> > > > >
> > > > > commit 16f039b1545efc8c2e045ee203bdde4e85b227d1
> > > > > Author: Douglas R. Reno <[email protected]>
> > > > > AuthorDate: Wed Apr 30 21:11:18 2025 -0500
> > > > >
> > > > > glib-networking: Document how to use libproxy.
> > > > > ---
> > > > > networking/netlibs/glib-networking.xml | 7 +++++++
> > > > > 1 file changed, 7 insertions(+)
> > > > >
> > > > > diff --git a/networking/netlibs/glib-networking.xml
> > > > > b/networking/netlibs/glib-networking.xml
> > > > > index 4946dfad99..3c5cc8e4aa 100644
> > > > > --- a/networking/netlibs/glib-networking.xml
> > > > > +++ b/networking/netlibs/glib-networking.xml
> > > > > @@ -141,6 +141,13 @@ ninja</userinput></screen>
> > > > > <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
> > > > > href="../../xincludes/meson-buildtype-release.xml"/>
> > > > >
> > > > > + <para>
> > > > > + <parameter>-D libproxy=disabled</parameter>: This
> > > > > switch disables libproxy
> > > > > + as the majority of users do not need it. If you use a
> > > > > proxy server, make
> > > > > + sure you have the <xref linkend="libproxy"
> > > > > role="nodep"/> package
> > > > > + installed and remove this option.
> > > > > + </para>
> > > > I don't think this explanation is correct. For using a proxy
> > > > server
> > > > it's only needed to build with gsettings-desktop-schema and
> > > > configure
> > > > the proxy server via gnome-control-center or just a gsettings
> > > > command.
> > > That's a good point, I wasn't aware of that! Should we mention to
> > > enable
> > > it for "automatic" configuration instead?
> > I don't know. Maybe it needs libproxy (built with duktape) to
> > handle
> > the PAC file or not.
> >
> > To me the main point of libproxy is to propagate the system proxy
> > setting (for example the one in gsettings) to all applications using
> > libproxy. I don't have a way to test it: even without it Firefox
> > still
> > picks up my proxy setting from gsettings if I select "use system
> > proxy
> > setting" in the Firefox about:preferences, and if I select "manually
> > configure the proxy" and enter the proxy setting it works as well.
> > Thus
> > the explanation in Firefox is incorrect too.
> >
> > And at the very lease we are missing gsettings-desktop-schemas in
> > the
> > dependency list, so our libproxy build may *not* actually use the
> > proxy
> > setting in gsettings. I don't think it's a good thing: maybe adding
> > libproxy will actually *break* the proxy setting chain in GNOME
> > then.
> >
> I think we originally added libproxy because of kio-extras, so I
> suspect
> something in KDE could be used to test it but I'm not sure.
> meson_options.txt in libproxy shows that the KDE configuration support
> is intended for usage with KDE System Settings.
>
> We definitely need to add the gsettings-desktop-schemas dependency to
> the book and mark it as either recommended or required. I just
> reviewed
> my logs and found the following at the end:
>
> Plugins
> Configuration Environment: true
> Configuration GNOME : true
> Configuration KDE : true
> Configuration Windows : true
> Configuration sysconfig : true
> Configuration OS X : true
> Configuration XDP : true
> PAC Runner Duktape : true
>
> It looks like "Configuration GNOME" is turned on by default, and the
> package won't build without gsettings-desktop-schemas (unless you add
> -Dconfig-gnome=false)
>
> Should I setup a pair of VMs (one LFS system and one Squid server) to
> help investigate? Breaking the proxy setting chain in GNOME would be
> very bad, and at the same time the lack of proxy settings in KDE
> applications could be problematic too for users impacted. I haven't
> touched Squid in a while but I do remember the basics of how to
> configure it.
If you have the time to do all these things...
Otherwise we can just say a vague "build with libproxy to allow this
package getting proxy setting via it" instead of the false "if you need
proxy you must have libproxy."
--
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University
--
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page