1 |
On Mon, Apr 30, 2012 at 2:42 PM, James <wireless@×××××××××××.com> wrote: |
2 |
> Michael Mol <mikemol <at> gmail.com> writes: |
3 |
> |
4 |
> |
5 |
>> Use a network-mounted distfiles directory on a common file server? |
6 |
>> That way, once you've downloaded it once, for any system, the package |
7 |
>> is right there for the rest. |
8 |
> |
9 |
> |
10 |
> Well I do not use NFS or such, but, I do scp the restricted files around. |
11 |
> My environment is such that it is partitions and systems moved around |
12 |
> too frequently (used remotely) to use a dist file system. |
13 |
> |
14 |
> So, I'd like to bypass the fetch restrictions all together... |
15 |
> one and for all; any other ideas? |
16 |
|
17 |
Patch Portage? Having a local patch like that would depend on whether |
18 |
or not the Portage ebuild supported particular hooks, but I don't |
19 |
remember the specifics. |
20 |
|
21 |
If you're using scp, you might consider using sshfs for your |
22 |
distfiles. Or, heck, dropbox. |
23 |
|
24 |
|
25 |
-- |
26 |
:wq |