On 10/09/2013 22:11, Timur Aydin wrote: > Today I had quite a bit of issues while creating a local overlay to > modify samba. Got through all of them, but there were the following > issues which I wanted to bring up, because I am not sure whether I have > done anything wrong: > > - I had created the overlay under "/root/overlay", but this is causing > "permission denied" errors from ebuild when creating the Manifest file:
Do you have userpriv set in FEATURES? That makes emerge run as portage which cannot read /root. Putting things like code, data and configs in /root is universally a bad idea. Do not do this. Put such things in the usual places, protected by orthodox permissions, just like every other package on your system. Your local overlay is no different to the tree and does not require special handling. [snip] > After trying many different things without luck, I tried using > /usr/local/portage as the overlay folder and the problem went away! So > my first question is, does ebuild have a special security feature which > prevents it from processing overlays under /root ? No, you just had the overlay in a highly unusual place. > > - The second issue is eclass related. After I moved net-fs/samba under > /usr/local/portage, I got the following error during Manifest creation: > > ====================================================================== > bonsai samba # ebuild samba-3.6.18.ebuild manifest > * ERROR: net-fs/samba-3.6.18::myoverlay failed (depend phase): > * pam.eclass could not be found by inherit() [snip] > To resolve this, I just copied /usr/portage/eclass to > /usr/local/portage/eclass. Is this a proper solution? No, that copies ALL the eclasses and is likely to really mess things up. In fact, you should not have had to do anything with eclasses at all. I suspect your make.conf is faulty. What is the contents of make.conf? what is ls -al $PORTDIR/eclass/pam.eclass -- Alan McKinnon alan.mckin...@gmail.com
