On 10/02/2014 19:03, Walter Dnes wrote:
On Mon, Feb 10, 2014 at 05:09:55PM +0000, Stroller wrote
On Mon, 10 February 2014, at 4:55 pm, Gleb Klochkov <glebiu...@gmail.com> wrote:
Hi. Try to use sudo with no password for eix-sync.
I'd really rather not. Thanks, though.
Being in group "portage" is not enough. That merely lets you do
emerges with "--pretend". "emerge --sync" modifies files in
/usr/portage. Files and directories in /usr/portage/ are user:group
root:root. Therefore you *NEED* root-level permission to modify them.
No ifs/ands/ors/buts. The overall easiest method is to (as root)...
Your are mistaken. The "usersync" FEATURE is a default. You can rename
your make.conf file and invoke portageq envvar FEATURES to verify this.
The consequence of this feature being enabled is that portage assumes
the privileges of the owner of /usr/portage. The entire point of this is
that portage doesn't have to exec rsync as root. Doing so is both
needless and dangerous.
Ergo, recursively setting the permissions of /usr/portage to
portage:portage is actually a really good idea. Indeed, you should find
that recent portage snapshot tarballs extract in such a way that portage
is both the owner and associated group.
The problem the OP is having concerns only the file modes, which is a
separate matter altogether.
--Kerin
