I brought this up a few weeks ago and didn't get a whole lot of response. Now that the 3.2.0b2 release has a nice set of httools, part of me would like to see htmerge become a real merge tool. At this point, what's left of the "cleanup" functionality is in htpurge. If I move htmerge into httools and make it a real database-merge utility, it will break a lot of people's scripts (including mine). The initial response when I brought this up was "that's fine if you make a big note." If I don't hear major complaints, I'm going to convert htmerge this weekend and update the rundig script accordingly. Here's how htmerge could act: htmerge -m merge-configfile [-c configfile] [-v] The -m flag could be used multiple times to loop through the specified config files, merging each one into the main config or the config specified by the -c flag. If the -m flag is not specified, it does nothing and exits. This would ensure some semblance of backwards-compatibility. The other option is to spit up a usage message, which would at least make people aware of the change. Right now I'm leaning towards the graceful exit. Thoughts? Complaints? -Geoff ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
