public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] about ccache permission adjusting
Date: Sat, 19 Nov 2005 11:11:33 -0700	[thread overview]
Message-ID: <7573e9640511191011j5a8373d2od611d8d0ade69763@mail.gmail.com> (raw)
In-Reply-To: <85901b690511190533x57175e4fgb23de50f7986d66e@mail.gmail.com>

On 11/19/05, sempsteen <sempsteen@gmail.com> wrote:
> Hi,
>  I've changed my CFLAGS settings and merged ccache for later works. Now i'm
> updating my system with "emerge -e world". During merge i realize that
> ccache is adjusting permissions for 4 times per package; before merge,
> before unmerge of existing packages, after unmerge and after merge. It's
> something like this:
>
>  --- !targe sym /usr/lib/libglib-2.0.so
>  * Adjusting permissions on ccache in /root/.ccache
>  >>> original instance of package unmerged safely.

First, there is no need to post your message multiple times.  Gmail
doesn't show your own postings to mailing lists, so you will not see
your message until someone resonds.  Also, you should only post in
plain text...no HTML/Rich formatting.

The Adjusting permissions is done in /usr/lib/portage/pym/portage.py. 
Basically, it makes sure that the ccache directory is owned by
root:portage, and is group writable.  If you use userpriv, it does the
same thing, but for owner portage:portage.

Actually, there is a problem in the code in that it also looks for the
SETGUID bit, but doesn't set it.  So if you want to avoid this, you
can set the SETGUID bit with:

chmod -R 02770 /root/.ccache

-Richard

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-19 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19 13:33 [gentoo-user] about ccache permission adjusting sempsteen
2005-11-19 18:11 ` Richard Fish [this message]
2005-11-19 19:08   ` sempsteen
  -- strict thread matches above, loose matches on Subject: below --
2005-11-19 10:59 sempsteen

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=7573e9640511191011j5a8373d2od611d8d0ade69763@mail.gmail.com \
    --to=bigfish@asmallpond.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