On 15/06/2019 10.52, dieter wrote:
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. I fully support the idea of a local caching mechanism.
But I am not convinced it is a good solution to pack this functionality into zypper. 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.
In the past I used wwwoffle to achieve such local caching because it was very easy to setup. The systems on the LAN used it for the updates. But wwwoffle is gone from the official repos, squid seems too much for this purpose, and I found no proper replacement yet.
The problem is that the actual download URL changes, depending on what the MirrorBrain answers each time is the best mirror. This makes using a proxy server more difficult. We would need some kind of special proxy cache that gets the requests from zypper directly, then does the download in the same manner that zypper would do it, save it locally in an structure that mimics the upstream directories, and serve the requests to the local LAN zyppers or yasts. It would be good for anyone maintaining several machines. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)