On Wed, Jan 14, 2009 at 11:57:02PM -0800, Ovid wrote: > > From: Patrick R. Michaud <pmich...@pobox.com> > > What's the rationale for the spectest suite to remain in the > pugs repository? 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.
Moritz already replied with why spectest is currently in pugs, I tend to agree. For now I'd like spectests to continue to have a very liberal commitbit policy, and that may or may not be compatible with Rakudo's commitbit policy (depending on how things end up). > 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). Being able to fudge against multiple implementations is the whole purpose of fudge. Agreed that it's not documented very well -- that's one of the things I'd like to fix via the Rakudo web site (that is also being discussed as part of this infrastructure topic). > 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. Currently I don't have to switch to a different repository or terminal window now -- I just edit the tests directly in t/spec/ and do commits as I normally would. It just so happens that those commits end up in the pugs repository instead of the Parrot one. Perhaps that approach doesn't work on other platforms, but thus far it's been working great for me. Pm
