When I run "ebuild ... digest" as a normal user, ebuild complains that I'm not root (Portage 2.0.27). This is the only thing that stops me from using root when doing some ebuilds. I really don't think I need to be root to actually create digest files. I understand that normally only root is allowed to write digest files because of directory permissions. But in this case, I cd'ed to a local directory (think /usr/portage.cvs) which the normal user has write access to. ebuild shouldn't complain in that particular case.
well, isnt the error stemming from file permissions and not the actual app ? if so, only root should have +w for /usr/portage/ also, root shouldnt need to build digest files for /usr/portage/ if its an issue of building custom ebuilds, then that is what the PORTAGE_OVERLAY variable is for ... set it to /usr/local/portage/ and give full user access to that directory
>well, isnt the error stemming from file permissions and not the actual app ? No. ebuild is complaining right away: $ PORTDIR=/storage/portage/tree.cvs /usr/sbin/ebuild pinepgp-0.18.0.ebuild digest !!! ebuild must be run by root. >if so, only root should have +w for /usr/portage/ I wasn't talking about /usr/portage. Of course /usr/portage should only be writable by root, but that isn't the matter here. I wanted to create a new ebuild where there is no digest file for it yet. For this, I have to run "ebuild ... digest". But I simply _can't_ as a normal user, because ebuild complains right away without actually _trying_ to write the file (which it could because of directory permissions). >also, root shouldnt need to build digest files for /usr/portage/ See above. >if its an issue of building custom ebuilds, then that is what the >PORTAGE_OVERLAY variable is for ... set it to /usr/local/portage/ and >give full user access to that directory As I see it, an _overlay_ is just that. You can _read_ from an overlay if it contains newer versions that the underlying storage, but you can't write to it. However, I don't know what ebuild does with PORTDIR_OVERLAY. drobbins should clear this up. (AFAIK, there is no documentation whatsoever on PORTDIR_OVERLAY yet except for the Portage changelog.)
sorry, i didnt see who posted the bug i usually make posts like that since most people who post bugs need to be walked like that ;) i guess you can disregard my entire first comment
Is this relevant with the advent of the 'portage' user? Can it be closed as FIXED?
Works here, although ebuild is in /usr/sbin by default, I'd like to see it in /usr/bin
