| 1 |
On Fri, Mar 25, 2011 at 11:52 AM, Nikos Chantziaras <realnc@×××××.de> wrote: |
| 2 |
> I noticed that recent versions of portage 2.1.9 create an ._unmerge_ |
| 3 |
> directory in /var/tmp/portage. What is it used for? |
| 4 |
|
| 5 |
Looks like this is the new PKG_TMPDIR. I think this is patch that made |
| 6 |
the change, with explanation: |
| 7 |
|
| 8 |
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=83e677766650e73071813c0d46547647e5f66029 |
| 9 |
|
| 10 |
"Before, some temporary directories would be created directly in |
| 11 |
$PORTAGE_TMPDIR. Now, all are subdirectories of |
| 12 |
$PORTAGE_TMPDIR/portage since it's common for people to assume that |
| 13 |
this is the case anyway. With the default PORTAGE_TMPDIR setting of |
| 14 |
/var/tmp, this allows /var/tmp to be mounted with the "noexec" option, |
| 15 |
as long as the /var/tmp/portage subdirectory is a separate mount |
| 16 |
(people have already tended to assume that they can do this, so we're |
| 17 |
making it a reality in order to avoid any more bug reports). This will |
| 18 |
fix bug #346899." |
Archives