>
> 1) For stability, I do not always keep constant with the DB package.
> Especially when ht://Dig is nearing a release, a code freeze includes
> the DB code.
> 2) I haven't had a chance to do a cvs import with the new version yet. ;-)
>
I'll add a third one : Berkeley DB on htdig CVS is patched to support
transparent compression. This patch will (hopefully) be included in Berkeley
DB but is not at present.
Cheers,
--
Loic Dachary
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 09 80, Fax: 33 1 56 96 09 61
e-mail: [EMAIL PROTECTED] URL: http://www.senga.org/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
- [htdig3-dev] Current CVS is broken Geoff Hutchison
- [htdig3-dev] Current CVS is broken loic
- [htdig3-dev] Current CVS is broken loic
- [htdig3-dev] G++ Woes (Was: Current CVS is brok... Michael Hirohama
- [htdig3-dev] G++ Woes (Was: Current CVS is brok... loic
- Re: [htdig3-dev] G++ Woes (Was: Current CVS... Torsten Martinsen
- [htdig3-dev] DB 2.7.7 (Was: G++ Woes (Was: ... Michael Hirohama
- Re: [htdig3-dev] DB 2.7.7 (Was: G++ Woe... Geoff Hutchison
- Re: [htdig3-dev] G++ Woes (Was: Current CVS... Michael Hirohama
- [htdig3-dev] Configure Error 1 (Was: G++ Wo... loic
- Re: [htdig3-dev] Current CVS is broken Geoff Hutchison
- Re: [htdig3-dev] Current CVS is broken loic
