On Thu, Mar 12, 2009 at 01:30:59PM +0000, Dominic Hargreaves wrote: > What should we do with this bug for request-tracker3.8? > > I quite like the idea of supporting sqlite out of the box and agree > that we can't automatically configure anything else reliably. > > It is also fairly clear that it's not recommended for use in any > production setting (except possibly for very low-use installations). > > It's already the case that anyone using our RT packages is going to have > to have some knowledge of these matters - RT is not a fire-and-forget > deployment even if we try and make it so as much as possible. > > Can we do any better than duplicating the documentation currently in > 3.6 in 3.8 (and moving the docs currently on the team's web space into > the package once we've had a chance to stabilise them?)
A dbconfig-common hook for adding comments to the dbc_dbtypes list along with something like "Recommends: rt3.6-db-mysql|rt3.6-db-postgresql" could work. The hook feels a bit bloatish and too special purpose, but I suppose it doesn't hurt to cook up a patch and ask the dbconfig-common maintainers for their opinion. I'll look at that. Meanwhile, I think the Lenny solution is adequate. I agree the docs eventually belong in the package itself. I don't expect this to be such a big thing for Squeeze: Jesse said there are just a few known issues with the SQLite backend, and the Lenny version + users of the 3.8 versions will probably give it more testing. Cheers, -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org