1 |
On Thu, Jan 27, 2011 at 9:16 AM, Natanael Olaiz <nolaiz@×××××.com> wrote: |
2 |
|
3 |
> Hi all, |
4 |
> |
5 |
> I want to make a live-ebuild for a private subversion repository. |
6 |
> I see in the developers manual [1] that CVS have the vars ECVS_USER and |
7 |
> ECVS_PASS, but cannot found equivalent ones for SVN [2]. |
8 |
> |
9 |
> Anyone knows what would be the prefered way to do that? Is safe to |
10 |
> include the login in the ebuild? Can it have only read permissions to root? |
11 |
> |
12 |
> |
13 |
> And a similar case: a .tar.gz source package which is on a private web |
14 |
> URL. What is the best way to download it from the ebuild? |
15 |
> |
16 |
> |
17 |
> Thanks in advance, |
18 |
> Natanael. |
19 |
> |
20 |
> |
21 |
> [1] |
22 |
> |
23 |
> http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html |
24 |
> [2] |
25 |
> |
26 |
> http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/svn-sources/index.html |
27 |
> |
28 |
> |
29 |
> |
30 |
Hi Natanael, |
31 |
|
32 |
I just took a quick look at the eclass that determines the behavior you are |
33 |
interested in, and the short answer is yes that is supported via ESVN_USER |
34 |
and ESVN_PASSWORD. I would strongly encourage you to read the actual eclass |
35 |
though, as it details other handy functionality too. That file is generally |
36 |
located in /usr/portage/eclass/subversion.eclass |
37 |
|
38 |
Now, as to whether to include the value ESVN_PASSWORD in the ebuild, I would |
39 |
not do that. Personally, I would setup svn+ssh and use an ssh key to access |
40 |
the repo. I do this with git using the git eclass. I am prompted for a |
41 |
password/key by portage in this case. To automate this using an ssh key, you |
42 |
can just use a passwordless key or setup ssh-agent. Also note, the key will |
43 |
be sought out first in /root/.ssh (I think it looks there first anyway). |
44 |
|
45 |
Regarding your final question, I think that portage will ask you to enter |
46 |
the password if it tries to access something over HTTPS requiring |
47 |
authentication, but I am not 100% certain at the moment. |
48 |
|
49 |
Regards, |
50 |
Matthew W. Summers |