Op een mooie zomerdag (Sunday 24 July 2005 14:18),schreef John E. Malmberg: > Nicholas Clark wrote:
... > > The best way to get the current source is with rsync. The master source > > repository is in perforce, and there isn't anonymous access to that. > > We don't tend to make snapshots, I think partly because everyone actively > > developing is very happy with rsync, and partly because snapshots seem to > > generate near zero feedback, suggesting the time is better spent > > elsewhere. (I suspect that the widespread use of rsync helps explain the > > lack of interest in specific snapshots. In effect every commit gets > > treated like a snapshot) > > > > There are a few paragraphs on what can be got with rsync in perlhack.pod: > > > > http://search.cpan.org/~rgarcia/perl-5.9.2/pod/perlhack.pod#Keeping_in_sy > >nc > > > > but most simply if you run > > > > rsync -avz rsync://ftp.linux.activestate.com/perl-current/ perl/ > > I suppose it would be simple if I had a stable rsync to run. However > rsync source as supplied depends on one of those fork() things to work. Another option is to install the Test::Smoke module from CPAN and configure it to use FTP so you can use the synctree.pl script to sync the perl source-tree(s). Contact me directly (on my cpan.org e-mailaddress) if you need any help with that. Good luck, Abe -- I think this requires more thought, therefore I'm excising the "promise" from perldelta and replacing it with more non-committal mumbling. -- Jarkko Hietaniemi on p5p @ 2002-05-27
