1 |
On 01/27/2011 09:05 AM, Matthew Summers wrote: |
2 |
> Now, as to whether to include the value ESVN_PASSWORD in the ebuild, I would |
3 |
> not do that. Personally, I would setup svn+ssh and use an ssh key to access |
4 |
> the repo. I do this with git using the git eclass. I am prompted for a |
5 |
> password/key by portage in this case. To automate this using an ssh key, you |
6 |
> can just use a passwordless key or setup ssh-agent. Also note, the key will |
7 |
> be sought out first in /root/.ssh (I think it looks there first anyway). |
8 |
|
9 |
In this case, you could potentially have a problem if you have |
10 |
FEATURES=userpriv enabled, since that would cause src_unpack to execute |
11 |
as the "portage" user. |
12 |
|
13 |
> Regarding your final question, I think that portage will ask you to enter |
14 |
> the password if it tries to access something over HTTPS requiring |
15 |
> authentication, but I am not 100% certain at the moment. |
16 |
|
17 |
In this case, depending on the FETCHCOMMAND behavior, you could have a |
18 |
problem with FEATURES=parallel-fetch since it launches fetches in the |
19 |
background. So, if background fetch doesn't fail gracefully, you might |
20 |
want to set FEATURES="-parallel-fetch" in /etc/make.conf. |
21 |
|
22 |
Also, you could set PROPERTIES=interactive in the ebuild, in order |
23 |
ensure that the fetcher is executed in the foreground. |
24 |
-- |
25 |
Thanks |
26 |
Zac |