On Mon, 28 Jan 2002, Neal Richter wrote:
> 1. Any opposition to using GNU indent to pretty up the code a bit? I
> don't care about the specific style options used.
Nope. I think the general feeling is that there shouldn't be any mandated
indentation (i.e indent this way or your patch won't be accepted). But I
clean up sections that I find messy myself.
> 2. It would be wonderful if there was a way to disable/enable different
> compile options in the Makefiles or configure script. Use -O0 rather than
> -O2, disable -g, etc. Pretty minor, and I've got it fixed for
> me... anyone else interested?
Sounds like a great idea, but this already works w/o modification:
CFLAGS="-O2" CXXFLAGS="-O2" ./configure
or my favorite:
make clean; CFLAGS="-g" CXXFLAGS="-g" make
> 3. Now that I've got my feet wet here, what exactly needs to be done to
> sync-up the current mifluz code with what is in the htdig/db directory?
> Are we picking and choosing or tossing the old stuff or what?
At the moment, I'm spending all my ht://Dig time on getting htdig-3.1.6
out the door. I've written 2002-02-01 in the release notes, so we'll
hopefully keep that.
After that, I'm going to merge the 3-2-x branch back into the main CVS
tree and start in on the mifluz merge. In the htword/, db/, and htdb/
directories, there are essentially no useful modifications from
ht://Dig. (We have some bugfixes, etc., but there obsolete relative to the
mifluz code coming in.) The htlib/ directory requires more careful
Then, of course, it's a matter of fixing up any mangling. I skimmed
through the API changes this afternoon and I think I understand what Loic
has done in the new mifluz versions.
There's also a small matter that the current mifluz requires the iconv
Get latest updates about Open Source Projects, Conferences and News.