Am Sat, 17 Sep 2016 10:36:28 -0400 schrieb Rich Freeman <[email protected]>:
> On Sat, Sep 17, 2016 at 9:54 AM, Bertram Scharpf > <[email protected]> wrote: > > > > On Saturday, 17. Sep 2016, 10:31:17 +0200, Kai Krakow wrote: > > > Am Tue, 13 Sep 2016 19:49:04 +0200 > > > schrieb Bertram Scharpf <[email protected]>: > > > > [...] > > > > > > You could > > > > > > # mount -o bind /usr/portage/tmp /var/tmp/portage > > > > > > and then point the portage tmp dir to that directory. From there, > > > ebuilds cannot see the .git of /usr/portage. > > > > As long as I do not set GIT_DISCOVERY_ACROSS_FILESYSTEM... > > I don't think that if you navigate upwards after following a bind > mount that you end up in the tree that was mounted. Ie, > /var/tmp/portage/.. = /var/tmp, not /usr/portage. With a symbolic > link it would resolve to /usr/portage unless the shell does something > clever. > > You can mount bind mounts into containers, and I'm pretty confident > the container can't navigate out into the rest of the filesystem that > way. True. This is why I suggested a bind mount and not a symlink. -- Regards, Kai Replies to list-only preferred.
