using an http proxy?

[Noah Leaman]

Is it possible to have an officially supported rsync service that  
listens on port 80 for people like us who cannot get standard rsync  
ports opened up on the firewall? Is there a technical reason why I  
can't be done or is it a resource issue?

-- 
Noah

On Mar 24, 2008, at 2:48 PM, Rainer Müller wrote:

> Bryan Blackburn wrote:
>> If you set the standard curl proxy environment variables (http_proxy,
>> FTP_PROXY, etc; see 'man curl'), this should get fetching of sources
>> to work through the proxy.
>
> According to ticket #13158 [1], you have to specify your proxy on the
> command line if using sudo, as it normally unsets environment  
> variables:
>
> $ sudo env http_proxy='foobar' port fetch $portname
>
> This is still missing from the HOWTO section in the wiki [2], but
> requested. Any volunteers? :-)
>
>> However, for selfupdate, which uses rsync, there isn't a way to use
>> the proxy.  I think in this case you have to use a subversion-based
>> repository instead.  For this you need to checkout MacPorts[1], then
>> updated your ${prefix}/etc/macports/sources.conf to point to the
>> location of the dports directory instead of the rsync:// line.
>
> Unfortunately if rsync is unavailable, there is no other way of  
> updating
> base than downloading sources and compiling manually. But the ports  
> tree
> can be synced with svn over HTTP/HTTPS.
>
> Rainer
>
> [1] http://trac.macosforge.org/projects/macports/ticket/13158
> [2] http://trac.macosforge.org/projects/macports/wiki/howto/
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users