I suspect that SQL database installations are sufficiently nonstandard that installation problems will increase. I wouldn't want to complicate the configure/make process any more unless it can clearly be done in a way that doesn't impact people who don't use SQL databases. The goals associated with putting the info in SQL databases seem sufficiently different from the goal of creating html archives that I think the default implementation should be to keep the code separate. Are there any important disadvantages to putting SQL support in a separate utility or utilities?
-- ------------------------------------------------------------------------------ Peter McCluskey | "To announce that there must be no criticism of http://www.rahul.net/pcm | the President, or that we are to stand by the | President right or wrong, is not only unpatriotic | and servile, but morally treasonable to the | American public." - Theodore RooseveltReceived on Tue 15 Jul 2003 11:46:29 PM GMT
This archive was generated by hypermail 2.3.0 : Sat 13 Mar 2010 03:46:12 AM GMT GMT