in reply to Re^4: 5.10 imminent?
in thread 5.10 imminent?

And the location of "the public ActiveState repository"? Several googles have not turned up anything promising.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^6: 5.10 imminent?
by ysth (Canon) on Apr 12, 2007 at 16:22 UTC
[reply]

      Okay, 20 minutes later and I have a version of rsync that seems to run, so I switched into a directory where I'd like the sources put and typed the advised command: 

      c:\Perl\src>rsync -avz rsync://public.activestate.com/perl-current/
receiving file list ... done
drwxr-xr-x        6592 2007/04/12 16:55:20 .
-rw-r--r--           6 2007/04/12 16:55:20 .patch
-r--r--r--       31992 2007/03/20 16:06:44 AUTHORS
-r--r--r--        6111 2006/06/13 20:28:51 Artistic
-r--r--r--     3776973 2007/02/27 13:20:45 Changes
...
-r--r--r--        1363 2006/06/13 20:29:38 x2p/str.h
-r--r--r--        3637 2006/06/13 20:29:38 x2p/util.c
-r--r--r--         944 2006/06/13 20:29:38 x2p/util.h
-r--r--r--       48960 2006/06/13 20:29:38 x2p/walk.c

sent 99 bytes  received 86198 bytes  232.29 bytes/sec
total size is 62055224  speedup is 719.09

      [download]

      Result. A 10 minute wait and exactly nothing transferred!

      Of course you say. If you don't have a copy of bleed perl to be updated, then there is nothing to do?

      Or maybe I'm using the wrong options?

      Or...

      Could I work out what I'm doing wrong (besides following the instructions slavishly)? Maybe, but if the desire is to encourage widespread partisipation in the smoking (Is that legal?) of bleed perl, then it would make sense to make it reasonably easy for people to do so. Without having to ask 20 questions and end up feeling foolish in the process. Because otherwise, those few (non-usual suspects) who decide they'd like to have a go, will stop before they get started.

      From my perspective, I prefer a link to an archive file that I can download because wget knows how to resume a broken download without needing to go through an ever more laborious process of working out how far it got last time and what has changed in the meantime. A download of 15 MB can take me 2 or 3 days. Stuff changes. ISP drop connections. Each time it resumes, there is more stuff at this end to sync, and more likelyhood that stuff at the other has changed. wget doesn't have this problem.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]
        Or maybe I'm using the wrong options?

        If that was the exact command, then yes. You just spectacularly listed out all the files. You have to put them somewhere...

          rsync -avz rsync://public.activestate.com/perl-current/ c:\perl\src

        [download]

        Once you get this up and finally running, it's even better than wget, because rsync will only transfer the deltas of changed files, and handles partially transferred files (following a network drop-out) correctly. Even if I don't sync up for a month, I'll only pull down a few dozen kilobytes of source in the following sync.

        Please don't give up. Perl hackers on Windows are in short supply.

        • another intruder with the mooring in the heart of the Perl

[reply]
[d/l]

In Section Seekers of Perl Wisdom