Re: port selfupdate, rsync, and tight firewalls
"Johnathan Gifford" <[email protected]> Tue, 05 Sep 2006 14:17:45 -0500
| Newsgroups | gmane.os.opendarwin.darwinports |
|---|---|
| Message-ID | <[email protected]> |
>>> On Tue, Sep 5, 2006 at 1:36 PM, in message <[email protected]>, James Berry <[email protected]> wrote: > Johnathan, > > No, we don't plan to change this in the very near term. Yes, we will > be changing it somewhere in the mid- term, but I can't tell you to > what it will be changed. There's some chance that we may move away > from use of rsync altogether, toward a more http- only solution like > subversion over http. Or that the rsync hostname will become: > rsync.macports.org. > > James > > Who is the who in 'we' that makes these decisions? Better yet, who should I try to convince that an http-only solution behind Subversion is a more practical solution for those of us behind tight firewalls. After all port 80 is always accessible. > On Sep 5, 2006, at 11:24 AM, Johnathan Gifford wrote: > >> With all the changes going on with the migration from DarwinPorts to >> MacPorts, is the rsync URL going to change when doing a selfupdate? >> Currently it is pointing to >> rsync://rsync.darwinports/org/dpupdate/dports. I need to know. The > > Note, that should be: > > rsync://rsync.darwinports.org/dpupdate/dports > Yep. I've got a fat finger, can you tell? :-) >> company I work has a very, very tight firewall that blocks rsync, ftp, >> and a bunch of other stuff. In order to get access to those >> protocols >> I have to request each port to be opened. On top of that, I also have >> to let the security folks know which server(s) or domain name(s) they >> can talk to so that access can also be restricted. Hence, why I >> need to >> know if the URL may change, especially the domain name. >> >> Argh.... Yes this bites, but it's better than finding each dependency >> for a piece of software and building by hand. >> >> ** Note to port software makers: Don't always list your ftp sites >> first, second and so on. Try to putting an http site as the second >> location for the code source archive. ** >> >> Thanks, >> >> Johnathan >> _______________________________________________ >> Darwinports mailing list >> [email protected] >> http://www.opendarwin.org/mailman/listinfo/darwinports