OK, I'll try some/all of the suggestions. I have a few comments- On Thu, Feb 26, 2009 at 12:06 PM, Patrick R. Michaud <pmich...@pobox.com> wrote: ... > A longer announcement should be hitting the list later today, > but for now the recommended build sequence for rakudo is: > > $ git clone git://github.org/rakudo/rakudo.git
I'm new to git- if there's already a rakudo directory, will "git clone" also be good for updating it? Or is the recommendation to build from scratch each time there's a new release? ... > Also, if building Rakudo from inside a Parrot tree (which > we're no longer really doing any longer), Hope your announce also includes an update to http://perlgeek.de/blog-en/perl-6/where-rakudo-lives.writeback which lists "Rakudo inside Parrot" first. Conceptually I prefer Rakudo under Parrot, as it emphasizes that Rakudo is one parrot-compatible language implementation among many. I also understand how it's easier to keep the dependencies in sync when Parrot is under Rakudo instead, so won't protest any further. -y
