Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 35 |
Nodes: | 6 (0 / 6) |
Uptime: | 29:24:49 |
Calls: | 322 |
Calls today: | 1 |
Files: | 959 |
Messages: | 81,834 |
Posted today: | 3 |
In order to make room in my root, I
subsequently moved /var/tmp/portage to a mounted usb stick and symlinked
it to /var/tmp.
Hi,
On 25/2/25 18:05, n952162 wrote:
In order to make room in my root, I
subsequently moved /var/tmp/portage to a mounted usb stick and symlinked
it to /var/tmp.
Have you tried mounting (or bind mounting) to /var/tmp/portage instead
of symlinking?
Regards,
Matt
I have a second question that's a follow up to that.
Does portage *remove* some files in /var/tmp/portage but retain others?
This is important to me because I want to use this system as a local
binary server to other gentoo systems and because I want to retain the
build environments.
Hi,
That's an option. It means I'd have to dedicate an entire volume to
that, but it's doable.
A bind mount will not require this.
Bind mount operation
  Remount part of the file hierarchy somewhere else. The call is: >     mount --bind olddir newdir
. . .
      After this call the same contents are accessible in two places.
-- `man 8 mount`
But if the unpack phase insists on doing a "mkdir /var/tmp/portage",
would that work with a mounted drive?
It seems to be `/usr/bin install`, fwiw. A full build log would make troubleshooting anything more than a stab in the dark.
Let's find out. Maybe it doesn't like the symlink?
In fact, it's hard for me to image that the unpack phase would fail on
that, it's just a first guess. I just want to understand what's going
on and be sure I'm not making some mistake that'll bite me later.
I don't know off the top of my head. If you really want to understand
what's going on you'll need to read the Portage sources.
Regards,
Matt