| 1 |
On Thu, Aug 25, 2005 at 12:05:11PM +0200, Paul de Vrieze wrote: |
| 2 |
> Why not create that directory in the /var/tmp/portage/package/ directory. |
| 3 |
> It would also safeguard against packages using files that they did not |
| 4 |
> request. Maybe in the future a similar thing could be done for patches |
| 5 |
> (when ebuilds finally get to specify which files from the files dir they |
| 6 |
> use) |
| 7 |
using $PORTAGE_TMPDIR/portage/$CATEGORY/$P/distdir atm |
| 8 |
Note the additional $CATEGORY dir; unless people scream, it's wise |
| 9 |
from where I'm sitting- it avoids potential $PORTAGE_BUILDDIR |
| 10 |
conflicts. |
| 11 |
Yes they're unlikely, but why allow for it? |
| 12 |
|
| 13 |
Re: patches, would be game, just not sure of a clean way how. |
| 14 |
|
| 15 |
And for the truly paranoid, had thought about transfering $FILESDIR in |
| 16 |
during verification. That's a bit much for local trees, but for |
| 17 |
remote tree's $FILESDIR will be $PORTDIR/$CATEGORY/$P/files simply |
| 18 |
because a place is needed to slap the files on the local fs. |
| 19 |
~harring |
Archives