On Sat, 08 Sep 2007 23:23:13 +0100 David Claughton <dave@encoresoup.com> wrote: > Hi, > > I've created the beginnings of a package for sqliteman (upstream site is > http://sqliteman.com). It's a GUI frontend for a well established and generally not that buggy backend - it doesn't make a lot of sense (to me at least) to package it in the current state. > The problem I have is this program, currently seems to have a few fairly > major bugs (for example it is impossible to run "insert ... values" > statements - upstream bug #17). That is such a major omission and such a small amount of work. SQLite is easy (comparatively) and there are numerous packages out there inserting new data all the time. A frontend that cannot support INSERT is pre-alpha IMHO. (I've written one and I maintain almost a dozen others.) After all, commands to SQLite are passed as SQL statements - plain text. The website does come across as more hype than substance. > What's my best course of action - ITP it now and work on completing the > package despite its current buggy state, or hold fire until the more > serious bugs have been resolved upstream? There's no problem keeping an ITP open for ages (I've got one v.old ITP due to upstream bugs and lack of development time but that's my own upstream project so sometimes that changes the way that people view such an old ITP.) The thing is to ensure that the ITP indicates that this isn't imminent (and why) as well as responding if anyone does check on the progress of the ITP. There are few deadlines in free software so even apparently small amounts of code can take significant amounts of time - are you sure you will still be interested in packaging it when the issues are actually fixed? Even if that is next year or longer? (Real life has a habit of destroying even the best laid plans - you and upstream.) If you are that motivated, maybe you should get involved in the development and work on some of the code yourself. :-) -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpBochQAq2ce.pgp
Description: PGP signature