On Thu, Jan 27, 2011 at 9:16 AM, Natanael Olaiz <nol...@gmail.com> wrote:
> Hi all, > > I want to make a live-ebuild for a private subversion repository. > I see in the developers manual [1] that CVS have the vars ECVS_USER and > ECVS_PASS, but cannot found equivalent ones for SVN [2]. > > Anyone knows what would be the prefered way to do that? Is safe to > include the login in the ebuild? Can it have only read permissions to root? > > > And a similar case: a .tar.gz source package which is on a private web > URL. What is the best way to download it from the ebuild? > > > Thanks in advance, > Natanael. > > > [1] > > http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html > [2] > > http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/svn-sources/index.html > > > Hi Natanael, I just took a quick look at the eclass that determines the behavior you are interested in, and the short answer is yes that is supported via ESVN_USER and ESVN_PASSWORD. I would strongly encourage you to read the actual eclass though, as it details other handy functionality too. That file is generally located in /usr/portage/eclass/subversion.eclass Now, as to whether to include the value ESVN_PASSWORD in the ebuild, I would not do that. Personally, I would setup svn+ssh and use an ssh key to access the repo. I do this with git using the git eclass. I am prompted for a password/key by portage in this case. To automate this using an ssh key, you can just use a passwordless key or setup ssh-agent. Also note, the key will be sought out first in /root/.ssh (I think it looks there first anyway). Regarding your final question, I think that portage will ask you to enter the password if it tries to access something over HTTPS requiring authentication, but I am not 100% certain at the moment. Regards, Matthew W. Summers
