On Thu, Apr 25, 2019 at 5:44 PM <n952...@web.de> wrote: > > So, I set up the rsync deamon on my "mirror server" host and the > /etc/portage/repos.conf/gentoo.conf file on the client machine, run the > recommended test and everything is just as described. I sync my client, and > am very happy. > > By coincidence, I happen to look in /var/log/emerge-fetch.log on the client > and discover that everything got fetched remotely, from, like gentoo.org and > rubygems.org, etc. > > What a disappointment! Is there something I still have to do? >
The repository and distfiles both need to be separately mirrored. Maintaining a distfiles mirror is a bit more complex as all your hosts probably don't have the same packages installed, and fetching distfiles for all the packages would use a ton of space (and bandwidth). For Gentoo official mirrors this is exactly what is done, but of course they get used by many users. What I have done at times is run apache on one host and serve out its local distfiles cache, and then list this as the first mirror in the list for my other hosts. So, they try to fetch from that host before going out to the internet. However, that doesn't do anything to ensure that the needed files are on that host. It just helps with @system packages and other packages the hosts have in common. That is an approach that doesn't really cost you anything and probably provides 75% of the benefit. It is also easy to do if you have a bunch of identical hosts and then yields 100% of the benefit (if they're truly identical I'd go a step further and set up a binpkg mirror as there is no point in building the same thing many times with the same flags). If you really want to run a full distfiles mirror I'm sure the infra scripts are floating around somewhere. It probably just amounts to running an ebuild fetch on every ebuild in the repo. -- Rich
