Several bits of functionality would be perfectly at home in Rosella, either directly translated into winxed or replaced with something similar-but-better. I keep that project pretty well tested and maintained, although it's not a suitable home for all these things (Pg and OpenGL being two obvious examples that don't belong).
If we add these projects to the test_all_* make target, and include them in plumage for easy access, I don't see there being any real hardship. Having criteria laid out for library inclusion is a good thing. cotto++ --Andrew Whitworth On Wed, Mar 21, 2012 at 2:15 PM, Christoph Otto <[email protected]> wrote: > On Wed, Mar 21, 2012, at 11:59, Andrew Whitworth wrote: >> On Wed, Mar 21, 2012 at 9:51 AM, Moritz Lenz >> <[email protected]> wrote: >> > I have tried to use the Pg lib to make a Perl 6 module that >> > interfaces with postgres. I've written a number of tickets about it >> > (I specifically remember some instabilities, and the inabiilty to >> > report errors properly). >> > >> > As it is, it's not very useful, but it could be, if anybody ever got >> > around to maintain it. I'd really appreciate that. >> >> There is a PL/Parrot project in the ecosystem which is probably a >> better home for this module than the parrot core repo. If it's going >> to get any love at all, that's where it would happen. > > If Parrot's intended as a foundation for HLLs and libraries, we should > only keep libraries in core that match one of the following criteria: > The library should be necessary for the Parrot build, be something > that we expect most HLLs to use as-is, or show library hackers how to > do something that they'd have trouble finding elsewhere. I'm happy > moving anything else into a separate repo, either a junk drawer or a > dedicated project. > > As an aside, I'm more than happy to see such projects added to > all_hll_test (which we can rename to test_all_the_things or something > more appropriate) so that they're less likely to end up bitrotted. _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
