1 |
On Thu, 02 Jan 2014 11:10:54 -0500 |
2 |
Ian Stakenvicius <axs@g.o> wrote: |
3 |
|
4 |
> ..or we could just do this, using the existing RESTRICT="mirror" |
5 |
> that's already in ebuilds -- have a DISTDIR and a NODISTCACHEDIR, |
6 |
> NODISTCACHEDIR defaults to DISTDIR; if RESTRICT="mirror" then |
7 |
> distfiles are saved to NODISTCACHEDIR, otherwise are saved to DISTDIR. |
8 |
|
9 |
IMHO, this is the best solution proposed so far. It doesn't need a new |
10 |
USE flag duplicating information which is already in RESTRICT (or am I |
11 |
missing some corner cases here?), and it doesn't bother those who don't |
12 |
care about this issue with new distfiles-*/ dirs, as with Kent's |
13 |
proposal. |
14 |
|
15 |
@Kent: Why do you think another distinction for RESTRICT=fetch is |
16 |
neccessary? If it really is, it could also be integrated into this |
17 |
solution, but I don't get the point -- either you're allowed to |
18 |
redistribute it, or you're not. RESTRICT=fetch just signals Portage |
19 |
that it won't be *technically* able to download the distfiles. |
20 |
|
21 |
|
22 |
Luis |