Hi, in the light of current events, I would like to start to discuss a scheme for improving the regular Tumbleweed upgrade performance. 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. If ZYPPERCACHE is set and reachable, all files must be fetched though it. If ZYPPERCACHE is set and not reachable, zypper may (interactively) warn about it, and proceed as usual. Such a scheme would greatly relieve the load on the public infrastructure, and improve the upgrade performance of local systems significantly. I'm using a shared /var/cache/zypp/packages scheme already, that improves the situation already, but suffers from a couple of issues: two zypper processes are treading on each others feet, the repo definitions have to be synced carefully, it's hacky, etc... I think, that his great product deserves a decent solution to this problem. If it works well, other openSUSE distributions may profit as well. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org