On Sat, Sep 17, 2016 at 9:54 AM, Bertram Scharpf <li...@bertram-scharpf.de> 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 <li...@bertram-scharpf.de>: > > > > > The rfkill make suite looks for a version number and in case > > > the work directory is a Git repo it tries to query the > > > version number there. Then, it finds the Git repo in > > > /usr/portage and fails. Not very friendly! > > > > 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. > > I decided to add the following line to /etc/portage/make.conf: > > GIT_CEILING_DIRECTORIES="$GIT_CEILING_DIRECTORIES:$PORTAGE_TMPDIR" > > This should be part of the documentation. Where do I best > report it? Well, for anything on the wiki I'd suggest just adding it. For the manpages I'd submit a bug on bugs.gentoo.org against portage (the software). -- Rich
