Re: packaging sqliteman
Neil Williams wrote:
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.
Yes, I certainly wouldn't want a user to get a false bad impression of
sqlite through the use of this program - an aspect I hadn't considered.
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.
I picked sqliteman purely because I needed/wanted a GUI frontend (there
isn't a similar program already in Debian AFAICT) and this was one of
only a handful I was able to find on Google...
Perhaps I would be better to just go back and look a little harder! ;-)
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.)
I think, on reflection, I'll hold off for now, and keep an eye on
progress upstream, while also looking for an alternative GUI that may be
in better shape.
I would still like to see such an application in Debian, as well as
finding a usable program for my own use, of course :-)
Thanks for your advice,
David.
Reply to: