On 04/30/12 14:50, Michael Mol wrote: > On Mon, Apr 30, 2012 at 2:42 PM, James <wirel...@tampabay.rr.com> wrote: >> Michael Mol <mikemol <at> gmail.com> writes: >> >> >>> Use a network-mounted distfiles directory on a common file server? >>> That way, once you've downloaded it once, for any system, the package >>> is right there for the rest. >> >> >> Well I do not use NFS or such, but, I do scp the restricted files around. >> My environment is such that it is partitions and systems moved around >> too frequently (used remotely) to use a dist file system. >> >> So, I'd like to bypass the fetch restrictions all together... >> one and for all; any other ideas? > > Patch Portage? Having a local patch like that would depend on whether > or not the Portage ebuild supported particular hooks, but I don't > remember the specifics.
Won't help because the tarball location isn't in the ebuild. You have to go to the webpage to find it. You can patch the ebuild every time, but that takes the same amount of work (on each machine) as wget <foo>.
