public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@primate.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: /var/cache/edb
Date: Wed, 14 Dec 2016 14:25:06 -0800	[thread overview]
Message-ID: <20161214221429.6078.34AFCD6E@matica.foolinux.mooo.com> (raw)
In-Reply-To: <CAJ0EP41hQvX-xtLkf8x_QOvjHmVE=1DdMX4mpsHOmDLa59jaSw@mail.gmail.com>

On 2016-12-13 23:19, Mike Gilbert wrote:

> The dep subdirectory contains cached dependency information for
> ebuilds. It only gets populated if you locally modify ebuilds on your
> system; otherwise, the metadata directory from the repository
> (/usr/portage/metadata) is used instead.

I see stuff in that subdirectory related to overlays I have enabled via
layman, and ebuilds provided by those overlays, even when I'm _not_
using these ebuilds but the ebuilds for the same packages provided by
gentoo itself.  Or so I hope - for all such overlays I've masked */* and
only unmasked the 1 or 2 particular packages I need, which aren't in
gentoo.

The true reason the directory bothers me is its permissions, and those
of the files inside.  They seem to be created as portage:portage, 0660.
Why is root:root 0640 not good enough for them?  Does that mean some
part of portage runs setuid/setgid to the portage user/group?

-- 
Please *no* private Cc: on mailing lists and newsgroups
Personal signed mail: please _encrypt_ and sign
Don't clear-text sign: http://cr.yp.to/smtp/8bitmime.html


  reply	other threads:[~2016-12-14 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  3:59 [gentoo-user] /var/cache/edb Ian Zimmerman
2016-12-14  4:19 ` Mike Gilbert
2016-12-14 22:25   ` Ian Zimmerman [this message]
2016-12-14 22:31     ` [gentoo-user] /var/cache/edb Rich Freeman
2016-12-14 22:45     ` Mike Gilbert

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=20161214221429.6078.34AFCD6E@matica.foolinux.mooo.com \
    --to=itz@primate.net \
    --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