Ideally it should be as simple as that; just set the http_proxy
Two concerns though--first of all, at certain times a workaround of mine
has been to put proxy info in etc/wgetrc (besides having http_proxy
defined). Bug 315421 has the story. I have not checked if the etc/wgetrc
workaround was needed only for a couple of days, or if it is still needed.
Second, the `emerge --sync' step causes subversion to be used. It seems
that subversion requires ~/.subversion/servers to be set up. Long ago I
wrote a helper script that tries `emerge --sync' once (causing the
~/.subversion directory to be set up), and on failure adds the proxy
info into the servers file, and retries `emerge --sync'. Quite kludgy
but it solves the problem.
So, if it can't be helped that an HTTP proxy requires non-trivial steps
to be taken then IMHO the webpage should provide advice. Otherwise there
will be mail threads like this one, and bugs filed, and worst of all,
potential enterprise users will ditch Gentoo Prefix because it does not
> i just followed the proxy note from the gentoo handbook. i believe you
> have to use what works for wget, curl, or lynx.
> export http_proxy="http://proxy.server.com
> export ftp_proxy="http://proxy.server.com
> something like that should work depending on your shell.
> On Thu, 20 May 2010, firstname.lastname@example.org wrote:
>> The "Gentoo Prefix Use Cases" paper
>> (http://www.gentoo.org/proj/en/gentoo-alt/prefix/usecases.xml) has
>> scenarios where Gentoo Prefix is used in enterprise environments. It is
>> not unusual that machines in such environments have Internet access
>> through some kind of HTTP proxy.
>> I think it would be a good idea for the step-by-step instructions (e g
>> http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml) to
>> include recommendations on how to specify an HTTP proxy for the bootstrap
>> process. Perhaps it is not easy to cover all possible proxy
>> configurations, but probably it would go a long way to just indicate how
>> to do in a typical case.
>> Some time ago I found that putting proxy details in etc/wgetrc
>> appeared to
>> solve the problem for me. Recently this doesn't work anymore
>> Proxy info is also needed in ~/.subversion/servers; at least that is what
>> I have. It would be nicer if the subversion config files could be folded
>> into the prefix tree, I haven't looked into this.
>> Maybe there is more to it that I can't think of now. Anyway, if someone
>> adds instructions to the step-by-step page I volunteer to try them out.
>> --Rabbe Fogelholm