Am Samstag, 15. Juni 2019, 10:52:02 CEST schrieb dieter:
On Sat, 15 Jun 2019 09:06:18 +0200 Hans-Peter Jansen wrote:
Hi,
Given the following scenario: a local LAN with a couple of Tumbleweed installations, and optionally a server.
I) a modification of the zypper download lib to honor an environment variable, e.g. ZYPPERCACHE, and relaying the downloads to that system (server), if set II) a zypper caching server, that uses the zypper download lib, but implicitly keeps the downloads for later reuse.
But I am not convinced it is a good solution to pack this functionality into zypper.
Obviously, I didn't express myself correctly. The idea was to either * reuse the zypper download library * or recreate it in some high level programming language. Sorry, I also was not precise with my answer, I meant to express zypper or the zypper (download) library. I have to admit I am not familiar with
On Sat, 15 Jun 2019 12:11:32 +0200 Hans-Peter Jansen wrote: the existing functionality of the zypper download library, it just seems to me that this would be a quite big additional functionality. Especially to serve its local zypper-cache directory to other hosts.
In principle "some" local caching (http) proxy on one of the systems would be sufficient for this purpose, and zypper on the different systems accesses it just by proxy settings.
I even created a squid plugin for this purpose once, but with squid alone, this isn't the real McCoy either, because intercepting SSL connections is no fun.. But, given (I) is available, we could use squid as a proxy, and point ZYPPERCACHE to a local http address. BTW, what I don't like much about squid is the way, it stores the cached items. I would much prefer a directory layout like zypper is using itself. In my experience up to now SSL interception is not necessary, the openSUSE download URLs are still accessible via http protocol.
Regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org