I've just setup a Subversion mirror of the parrot cvs repository with
svk. Will try to keep it in sync until Robert have time to do similar
setup on perl.org.
So you could now use the Subversion repository (readonly) at:
svn://svn.clkao.org/parrot/cvs/trunk
web interface at http://svn.clkao.org/svnweb/parrot/
and for people with unfortunate per-minute metered ISDN, svk could be
used to mirror the above url, create local branch and do commits
locally. Later on generate a diff to apply to cvs, or if the
development trunk switches to svn it would be even eaiser.
Hopefully this could eventually allow more time for fine white wine
while retaining the same excellent productivity.
Cheers,
CLK
Cool!
One thing though. Checking this out on Mac OS X runs into the problem
of the PLATFORMS file and the platforms directory conflicting due to
case sensitivity problems. Looking in
http://cvs.perl.org/viewcvs/viewcvs.py/cvs-public/parrot/ there doesn't
seem to be a 'platforms' directory in the current parrot CVS, so why is
it showing up in the mirrored copy?
-garrett
There used to be a platforms directory, but it went away for just
this reason. Remnants of it show up from time to time. :(
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
You need to set the svn:executable property on icu/source/configure,
or compilation will fail.
--
bd
I thought that subversion was tried for use with Parrot and found
unexceptable for some reason a while back. I am not trying to
discourage you guys... I personally prefer svn to cvs, but I think it
would be wise to determine of those problems still exist.
Matt
IIRC, we tried it for ponie, and the problem was that it took an insane
amount of time to perform a simple checkout or update operation. But
that was largely because of the combined girth of Parrot and Perl
5--Parrot by itself should be much more manageable.
Not to say that Subversion might not still be too slow for Parrot--just
that we can't be sure it is until we try, and this seems like a much
wiser way to do so than converting the master repository.
--
Brent "Dax" Royal-Gordon <br...@brentdax.com>
Perl and Parrot hacker
Oceania has always been at war with Eastasia.
> Matt Fowles wrote:
>
>> I thought that subversion was tried for use with Parrot and found
>> unexceptable for some reason a while back. I am not trying to
>> discourage you guys... I personally prefer svn to cvs, but I think it
>> would be wise to determine of those problems still exist.
>
>
> IIRC, we tried it for ponie, and the problem was that it took an insane
> amount of time to perform a simple checkout or update operation. But
> that was largely because of the combined girth of Parrot and Perl
> 5--Parrot by itself should be much more manageable.
>
> Not to say that Subversion might not still be too slow for Parrot--just
> that we can't be sure it is until we try, and this seems like a much
> wiser way to do so than converting the master repository.
>
It was also a rather long time ago, before subversion 1.0, and many
performance problems were fixed in the meantime.
-garrett
It was a protocol problem, one that's been fixed as I remember. I'd
still like a good shakedown by someone a long way away as the packet
flies before considering switching, but I think things are a lot
better.
* It'd be easier for me to follow the development.
* I could make offline branches if I start hacking parrot.
* Vendor branches could be maintained more easily for things like
ponie that needs to embed parrot.
* People might find some the above true for them too.
It's more about interpolating (like parrot!) than enforcing.
On Sat, Aug 07, 2004 at 07:00:41PM -0400, Matt Fowles wrote:
> I thought that subversion was tried for use with Parrot and found
> unexceptable for some reason a while back. I am not trying to
> discourage you guys... I personally prefer svn to cvs, but I think it
> would be wise to determine of those problems still exist.
Cheers,
CLK
> I've just setup a Subversion mirror of the parrot cvs repository with
> svk. Will try to keep it in sync until Robert have time to do similar
> setup on perl.org.
> So you could now use the Subversion repository (readonly) at:
>
> svn://svn.clkao.org/parrot/cvs/trunk
>
> web interface at http://svn.clkao.org/svnweb/parrot/
Thanks -- this will be useful for folks to use to try it out.
On the plus side, I was able to build and install subversion-1.1.0-rc1
with no problems on Solaris 2.8. That's new since last time I looked at
subversion.
On the minus side, it's still slow (initial checkout took 41 minutes,
compared to 8 for CVS, though I can't say for sure how much of that was
due to the different hosts or network connectivity).
On the depends-on-how-you-look-at-it side, it still gobbles up local disk
space with its duplicate copy of everything. I understand there are good
reasons for doing that.
--
Andy Dougherty doug...@lafayette.edu
41 minutes? Subversion checkout takes 2m14s for me, as compared to CVS 1m.