public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Emerge interferes with Git (Was: Wlan disappeared after suspend)
Date: Sat, 17 Sep 2016 10:36:28 -0400	[thread overview]
Message-ID: <CAGfcS_=6Uzeh-0gzmdEpXr5yzYJvtWBtE9Do1r_Ey_U0qDWqOg@mail.gmail.com> (raw)
In-Reply-To: <20160917135428.GA8623@becker.bs.l>

On Sat, Sep 17, 2016 at 9:54 AM, Bertram Scharpf
<lists@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 <lists@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


  reply	other threads:[~2016-09-17 14:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  8:23 [gentoo-user] Wlan disappeared after suspend Bertram Scharpf
2016-09-13 12:08 ` Michael Orlitzky
2016-09-13 13:12   ` [gentoo-user] Emerge interferes with Git (Was: Wlan disappeared after suspend) Bertram Scharpf
2016-09-13 15:12     ` Rich Freeman
2016-09-13 15:19       ` Michael Orlitzky
2016-09-13 17:49       ` Bertram Scharpf
2016-09-17  8:31         ` [gentoo-user] " Kai Krakow
2016-09-17 13:54           ` Bertram Scharpf
2016-09-17 14:36             ` Rich Freeman [this message]
2016-09-17 15:18               ` Kai Krakow
2016-09-18  2:41               ` Bertram Scharpf
2016-09-13 13:18   ` [gentoo-user] Wlan disappeared after suspend Bertram Scharpf
2016-09-13 13:22     ` Michael Orlitzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_=6Uzeh-0gzmdEpXr5yzYJvtWBtE9Do1r_Ey_U0qDWqOg@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox