On Friday 28 of January 2011 15:26:27 Donnie Berkholz wrote: > On 11:55 Thu 27 Jan , Zac Medico wrote: > > On 01/27/2011 11:08 AM, Matthew Summers wrote: > > > One question though. Since the 'portage' user has its $home set by > > > default to /var/tmp/portage how would you recommend handling the ssh > > > key situation since that directory is somewhat special? > > > > Well, I've never tried it, so I don't have any recommendation atm other > > than to make sure FEATURES=userpriv is not enabled. > > > > Moving forward, maybe it would make sense to have a notion of a > > configurable "fetcher home" that package managers and live/vcs eclasses > > would use for the HOME variable only when fetching. For example, the > > user could configure this by setting a FETCHER_HOME variable. > > This might be useful in other scenarios besides fetching that just > haven't occurred to us yet. Perhaps we should treat the portage user as > a regular user with a regular home directory that can be configured as > desired, and flip in and out of that user on demand.
Having SCM distfiles in user directory is not new 'market demand'. Below there's subversion eclass enhancement request I opened some time ago which I used to work around so far by denying emerge write access to distfiles. https://bugs.gentoo.org/show_bug.cgi?id=277976 -- regards MM
signature.asc
Description: This is a digitally signed message part.
