Ovid wrote: > ----- Original Message ---- > >> From: Patrick R. Michaud <pmich...@pobox.com> > >> Source code repository >> ---------------------- >> This is the immediate issue at hand, because we need to move Rakudo >> out of the Parrot repository so that it can cleanly move to its new >> home at parrot.org. Currently Rakudo Perl lives at >> http://svn.perl.org/parrot/trunk/languages/perl6/ , while the >> spectest suite (on which development/testing depends) lives at >> http://svn.pugscode.org/pugs/t/spec/ . > > What's the rationale for the spectest suite to remain in the pugs repository?
1) Many people have commit access to the test suite, and it's a good entry point for the new Perl 6 programmer. I'd like to keep access as liberal as possible. 2) There are other projects (namely elf atm) that use the test suite and live in pugs repo. 3) If we'd move it out of the pugs repo, I would rather have it as a completely separate project; keeping it in the repo of another implementation seem unfair, because none is more official than another 4) The synopsis live in the pugs repo; it feels good to have the test suite close to them. > AFAICT, pugs is no longer being actively developed and I wouldn't be > surprised if many of its spectests currently break and don't have a TODO. > Plus, the way fudge works, you have to be able to fudge things against both > pugs and rakudo, making things rather confusing (and it's not documented very > well that I can see, so I was royally confused at first). In fact, I think > that might even eliminate the need for fudge if done right. > > Why not bite the bullet and include those tests in Rakudo? If they're not > listed in t/spectest.data, they don't get run. Plus, it will make it much > easier for a developer to write tests and to review them because they don't > need to switch to a different repository or terminal window. Thus, a > developer won't need to have (or even know about) a separate repository *just > for tests*. That just seems weird. We're in Perl culture. Tests are known to be important here. Don't even dare of speaking of "just [for] the tests" ;-) > Merging the test suite and eliminating fudge seems like a great > simplification to me. We need fudge for keeping the tests implementation agnostic (remember, we're not writing the Rakudo Regression Test Suite, but the Official Perl 6 Test suite). We can do with #?rakudo whatever we like to make the tests run, and don't compromise on the tests themselves. That's incredibly valuable. Cheers, Moritz
