![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
On 07/26/2017 12:03 AM, Felix Miata wrote:
Repo caching for me, and locking/unlocking particularly, in openSUSE works fabulously, as does the vast majority of the zypp-based system. Other package management systems by comparison I find hopelessly deficient.
Very interesting. If I had more than one currently updating box (I have a half-dozen+ with working installs back to SuSE 9.0 in the bone-yard), I would revisit my local update server setup. In the 10.x - 11.0 days (and days of 1M WAN -- or heaven forbid dial-up) when running all SuSE/openSuSE boxes, I did full-repo package caching with full local repo hosting with createrepo, repo-signing, etc..., and it worked flawlessly. Basically all packages installed or updated (with download.use_deltarpm=false, keeppackages=1 set on local boxes) were rsynced to my local web-server, duplicates removed and createrepo run and the repo signed for each release and made available via apache. (not mirroring the full repos, just adding to my repo all packages that were downloading during the normal install or update process) That made new setups (which I did much more frequently in the past) a breeze with all needed (and updated) packages available via the LAN. Looking, 11.1 was the last release I did that for, I've never tried anything similar with apt, but for pacman, the exact same thing can be done with no more (and now arguably less) effort than caching for zypper. (essentially you can set to poll and update from any machine on your LAN and pacman will choose the repo based on timestamps) So there is hope for others :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org