On Tue, Feb 24, 2009 at 12:33:01PM +0300, z wrote:
2009/2/23 Duncan Mac-Vicar P. <dmacvicar@suse.de>:
I have submited libzypp 6.1.0 to Factory. Which makes aria2c the default transfer backend for http/ftp.
Read about what this means and some new features here:
http://duncan.mac-vicar.com/blog/archives/507
I wanted to test a little more, but Factory still has 5.11.0 which is even older than 11.1 updates I think. So be sure to read the post and learn about ZYPP_ARIA2C=0 in case something breaks or you are hit by any regression (may be open issues with proxy, ipv6) ;-)
Have fun!
Btw, this new stuff just arrived in Factory an hour ago.
Duncan Mac-Vicar P. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
hi. Am i right, that this will affect proxy management for yast\zypper? There was issue https://bugzilla.novell.com/show_bug.cgi?id=458708 due to curl environment vars for proxy can it be handeled gracefully since now? Thanks in advance
It will affect proxy handling in so far that the new download backend has slightly different characteristics of how it opens connections, does its HTTP requests -- changes on that level. What's unchanged is that any system-wide proxy setting is propagated to the download backend as before, with the little difference that .curlrc isn't relevant anymore. (Unless the old download backend is used, that is; but it should not be used anymore by default now.) However, it is an interesting question how to actually deal best with proxies. Since the new download backend uses more than one connection and downloads files in chunks, this does not play well with caching, and I am considering a procedere where we actually use the old backend when a proxy is configured. This or a configuration of the new backend that has the same effect. And since HTTP redirects do also not play well with caching (regardless of download backend), I am further considering the introduction of server-side state tracking. Anyway, once we have the newk powerful client, which deals with all the error scenarios that plagued users the past, optimizing for intermediary caches is one of the next things to have a closer look on. And I expect that it'll take a while until the new technical possibilities become reflected in YaST. So I'm talking rather low-level here, which may not completely answer your question to your satisfaction. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org