On Wed, 2010-04-07 at 13:25 +0100, Zhang, Qiang Z wrote: > 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?
libproxy goes through the GConf because it's using its GNOME backend. In MeeGo that's the way we currently store our proxy information so it does the right thing. Using libproxy not only enable your app to support Proxy auto-config, but also acts as an abstraction layer; if someone decides that proxy information should be stored in a different way, your application will still work. Now why is it a good idea to use GConf keys Firefox uses? It's because both chrome and Firefox use them (directly, not through libproxy) so it does not break those apps while keeping a single place to put the system-wide proxy configuration. I'm not sure what you need to do, but with you mentioning libzypp, I'm guessing you are trying to make Zypper aware of the system-wide proxy settings, something we (David Woodhouse) have done for yum in MeeGo (well, python-urlgrabber, see the MeeGo distro patch). In that case, it'd be nice to have Zypper use libproxy (or fallback to using it if the current way of specifying a proxy for Zypper returns an empty string). HTH, -- Damien _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
