Consider this use case: 1. Joe has a desktop machine in his home that's nearly always on, or a file server running Fedora. 2. Joe also has a laptop, both machines run the latest Fedora 3. Joe wants to make updating his laptop faster, and ticks the "share downloaded packages with others" button in the package updater, on his desktop (or server) 4. Joe's laptop automatically picks up that there is a local cache for files, and uses it to get cached packages Some security considerations: - don't download non-GPG signed packages from local caches - download repository information from upstream The point of the exercise is that it's one button to tick on the machine that will provide the cache (advertised via zeroconf/mDNS), and either an opt-in or automatic setup on the client (another box to tick, or a package to install to enable the functionality) Something similar exists for apt-get based systems: http://askubuntu.com/questions/3503/best-way-to-cache-apt-downloads-on-a-lan https://wiki.ubuntu.com/AptAvahi
My understanding of this RFE: It is addressing multiple machines sharing their content within the local network, thereby avoiding a trip to the external internet repos. Below are some links addressing this concept with yum: http://yum.baseurl.org/wiki/YumMultipleMachineCaching http://james.fedorapeople.org/yum/avahi/
This is a very old request that is not relevant to what pulp is today. Please re-open if you believe it pertains to pulp 2.2 or later.