Patrick R. Michaud wrote:
On Tue, Jan 27, 2009 at 11:25:29AM -0700, Stephen Weeks wrote:
Switching the rakudo repository to git means that it would
likely live on github, at least for a short time. We'd also
have to provide mechanisms for people to continue to obtain
and be able to easily commit to the pugs subversion repository.
The existing mechanism (makefile calls svn to check out t/spec) will
work fine unmodified with rakudo in git.
...assuming that the system also has subversion installed and
readily available.
Sure, but we assume that now. :-)
To register my current thoughts here on the list:
* I don't have much of a preference either way from the point of view of
my regularish hacking on Rakudo. On the one hand, I have to learn
something new. On the other, there may well be a win from that.
* Enough people who have worthwhile opinions on other stuff seem to rate
it, so I'm guessing there's substance rather than hype.
* Enough people on #parrot/#perl6 know it, that I'm happy I can get
hints as needed. Or just flame those who advocated it if I find it
sucky. ;-)
* I'm satisfied we can make a read-only svn frontend if need be, to keep
folks happy who just want to quickly grab a checkout to compile and
don't have git yet (since svn install base is wider).
If we have to move to git-hub before hosting elsewhere first, perhaps
let's set ourselves up a DNS CNAME alias, like git.rakudo.org. Then we
don't have to change repository URL a second time.
Thanks,
Jonathan
