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