[PATCH] Re: picking a date for subversion migration
Andy Dougherty
doughera at lafayette.edu
Fri Jan 30 13:18:13 UTC 2009
On Mon, 26 Jan 2009, Allison Randal wrote:
> The new repository is at https://svn.parrot.org/parrot.
>
> People using an svn client can change their existing checkouts over to
> the new repository with the 'svn switch' command. Running from the main
> directory of the checkout, that would be:
>
> svn switch --relocate https://svn.perl.org https://svn.parrot.org
I ran into a couple of issues:
1. perl.org also honored http:// as well as https://. parrot.org
only allows the https:// form. (This is an issue for me because my
build of svn doesn't understand https because, even after several
hours of hand-editing configure scripts, I couldn't get the build
system to find openssl consistently. (Some parts would;
other parts wouldn't. Long boring story.)
2. svn.perl.org also supplied an rsync mirror. The obvious attempt
to run the same command on svn.parrot.org fails. I don't know what
the plan is.
3. svn.perl.org provided regular snapshots. svn.parrot.org appears
not to do so. I don't know what the plan is.
I've patched docs/gettingstarted.pod to use the new address and put in
some NOTEs about things that need checking by someone who knows what's
going on.
Please note that I am definitely *not* trying to say whether or not
parrot.org should provide the snapshots, http://, and rsync access.
I fully recognize that each is an additional maintenance burden,
and that it is reasonable to decide that the cost of such additional
maintenance might outweigh the benefits. I am only trying to help fix
the documentation to accurately reflect reallity and to learn what steps
I need to take if I want to check out the parrot sources.
--- docs/gettingstarted.pod 2009-01-19 10:23:56.000000000 -0500
+++ docs/gettingstarted.pod.new 2009-01-30 07:59:17.000000000 -0500
@@ -22,45 +22,48 @@
There is a web interface to the subversion repository, in case you just want to
browse the source.
-L<http://svn.perl.org/viewcvs/parrot/>
+L<https://svn.parrot.org/parrot/>
=item *
The easiest solution is to grab the most recent snapshot of the Parrot SVN
repository. It's a tar-gzipped download of a recent checkout of Parrot, updated
every six hours. You can find it here:
+{{NOTE: This currently doesn't work.}}
-L<http://svn.perl.org/snapshots/parrot/parrot-latest.tar.gz>
+L<http://svn.parrot.org/snapshots/parrot/parrot-latest.tar.gz>
=item *
Even better is the option to use SVN, which gets you the very latest copy of
the Parrot distribution. The procedure for this is:
- svn checkout https://svn.perl.org/parrot/trunk parrot
+ svn checkout https://svn.parrot.org/parrot/trunk parrot
=item *
If you're one of those rsync folks, you can access the repository with:
+{{NOTE: This currently doesn't work.}}
-C<rsync -av --delete svn.perl.org::parrot-HEAD parrot>
+C<rsync -av --delete svn.parrot.org::parrot-HEAD parrot>
=item *
If you're using git-svn, you should check out just the latest version. First:
+{{NOTE: This is untested.}}
-C<< git svn clone -s -r HEAD https://svn.perl.org/parrot >>
+C<< git svn clone -s -r HEAD https://svn.parrot.org/parrot >>
=back
The above instructions are also on the Parrot website:
-L<http://www.parrotcode.org/source.html>
+L<http://www.parrot.org/source.html>
=head2 Now that I've got Parrot, what do I do?
Now that you've downloaded Parrot, you probably want to try it out. All you
-need is Perl 5.8.0 or later, a C compiler (any ANSI C compliant compiler
+need is Perl 5.8.4 or later, a C compiler (any ANSI C compliant compiler
should do - if you find one that doesn't work, please report it to us), and
some reasonable form of C<make>. To do this, follow these three easy steps.
@@ -213,6 +216,7 @@
As such, a better solution would be to submit your patch to RT, the request
tracker system that maintains bugs and patches for the Parrot project. To
visit RT, go here:
+{{NOTE: Needs to be updated for Trac }}
L<https://rt.perl.org/rt3/>
--
Andy Dougherty doughera at lafayette.edu
More information about the parrot-dev
mailing list