Brian Aker wrote: > Hi! > > One of the open projects that need to be started is refactoring the > command line applications. If someone was looking for a project I would > suggest taking a look at them. > > I would either start from scratch and build a new set of them or do a > mix of old and new. Pull them out of the main tree, and either include > them in libdrizzle, or just make them their own project (and if you > start from scratch please return them to their original licensing).
I'm voting strongly for its own project. It would be really nice to keep versioning on the library based on something real like API. Also, no matter how the tools are done, they are also going to wind up pulling in more depends, and keeping libdrizzle mostly build-depend-less is (I think) really important. > This is pretty low hanging fruit, but it would be nice to see those > programs revisioned as their own project. They are pretty damn stable, > so you start with a fairly GA'able project from the beginning. Have them > use libdrizzle and extend them to work with multiple open source > databases. There is no reason why these couldn't be GA'ed and carry on > their own life. I agree. I think it's pretty easy to do this in a couple of steps (no big rat-holes) 1) Finish removing depends on any code in drizzled/ mysys/ or mystrings/ from anything in client/ . 2) Move them out into their own programs. 3) Keep cleaning/make them nice! Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
