| 1 |
Neil Bothwick <neil <at> digimed.co.uk> writes: |
| 2 |
|
| 3 |
> > Now that I'm looking, it looks like a policy decision for the devs |
| 4 |
> > to formally evaluate. /distfiles/ should not be a dir for garbage, |
| 5 |
> > one-off-files and other such nonsense. |
| 6 |
|
| 7 |
> That's exactly what it is for. One-off files that the ebuild downloads, |
| 8 |
> uses and then no longer needs. Nothing in $DISTDIR is needed by a running |
| 9 |
> system. |
| 10 |
|
| 11 |
|
| 12 |
Ok so anything needed for a build of a particular package goes into |
| 13 |
/usr/portage/distfiles? |
| 14 |
|
| 15 |
I thought ebuilds use /var/tmp/portage for that. |
| 16 |
If in needs to hang around longer (than a /tmp file typically |
| 17 |
hangs out for, when not put it under the another logical place. |
| 18 |
|
| 19 |
Like I said I thought /distfiles/ contains compressed sources |
| 20 |
and other file needed, all rolled into a common format, like*.bz2. |
| 21 |
|
| 22 |
It we start (continue) strowing files into /distfiles/ where does it end? |
| 23 |
|
| 24 |
(folks, it's a philosophical discussion so no need to denegrate into |
| 25 |
crudedness), imho. |
| 26 |
|
| 27 |
|
| 28 |
James |
Archives