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