Mailinglist Archive: zypp-devel (38 mails)

< Previous Next >
RE: [zypp-devel] Make PackageKit zypp backend work using proxy
  • From: "Zhang, Qiang Z" <qiang.z.zhang@xxxxxxxxx>
  • Date: Wed, 7 Apr 2010 20:25:33 +0800
  • Message-id: <CF2F38D4AE21BB4CB845318E4C5ECB671D6A8AC6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Thanks. In fact, I have tried libproxy, but libproxy also call GConf API, so
libproxy also can't get the correct proxy info. Seems the runtime environment
is changed in libzypp.
Any comment?

-Thanks
-Qiang

-----Original Message-----
From: Dominique Leuenberger [mailto:Dominique.Leuenberger@xxxxxxxxxxxxx]
Sent: 2010年4月7日 18:11
To: zypp-devel@xxxxxxxxxxxx
Subject: Re: [zypp-devel] Make PackageKit zypp backend work using proxy

On 4/6/2010 at 15:45, Michael Andres <ma@xxxxxxx> wrote:
I'm not familiar with GConf. But before taking a GConf reader into libzypp,
I'd vote for using libproxy.

Very wise... gconf would be only looking at the gnome desktop... and once I
read that we also support KDE :)

A 'difficulty' in most cases, when it comes to PK is it's 'bare' way of
detecting proxy settings: It's much too inflexible and can't handle 'multiple
proxies' as used in various situations. If you want to use libproxy (or any
other reliable way of proxy handling.. does not really matter; libproxy
can only help you out) you need to pass every single URL to the proxy helper to
detect what the right proxy for exactly this URL would be (think about
pac files here).

think about a 'typical' setup:
- Repo 1: repo.mycomp.com/repository (internal, not reachable through our proxy)
- Repo 2: download.o.o/repositories/[...] (external, requires proxy).

Obvious the proxy settings vary from 'case to case'. Is PK reading 'proxy
ignore' variables? Which ones are supported?

(Of course you can s/PK/libzypp/ throughout the entire mail... it depends on
who is doing the downloading at the end... )

Dominique
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups