[livecd] fix /usr/portage/distfiles permissions

[GoogleCodeExporter]

The directory should has portage:portage permissions instead of root:root

As an example, I'm unable to upgrade the installer. It fails to create the 
svn-src directory

Original issue reported on code.google.com by blshkv on 12 Aug 2013 at 2:05

[GoogleCodeExporter]

I think the issue is that when I added the module for the nvidia and ati 
distfiles that things were added as root.  I'm not sure if I can fix it, since 
uid/gid is stored for owner, not actual username or group name afaik....

I think the sanest thing to do is just have a local.d/blah.start fix the 
permissions for us.

thoughts?

Original comment by sidhayn on 12 Aug 2013 at 3:47

[GoogleCodeExporter]

this is kind of not cool. I was hoping to fix the root of the problem.

Is it possible to hack livecd script and fix the permission after the directory 
has been created? 

Alternatively, we can try to set setuid and setgid flags on the directory.

Original comment by blshkv on 12 Aug 2013 at 9:08

[GoogleCodeExporter]

The directory is created on my system, outside the chroot, and then used on the 
livecd later.  How would you like to "fix the permission after the directory 
has been created" but not during runtime?

The portage user likely doesn't even exist when I create the module file, so 
it's not like I can look up the uid/gid from inside the chroot.

Original comment by sidhayn on 12 Aug 2013 at 1:09

[GoogleCodeExporter]

the portage userid is always 250:250. Does it help?..
You can run chown 250:250 and it will be properly owned after the portage user 
created

Original comment by blshkv on 12 Aug 2013 at 2:32

[GoogleCodeExporter]

well, yeah, yeah it does :-)  I'll fix now.

Original comment by sidhayn on 12 Aug 2013 at 2:38

[GoogleCodeExporter]

Committed revision 4886.

Original comment by sidhayn on 12 Aug 2013 at 8:03

• Changed state: Fixed