At 9:14 AM -0700 10/4/99, Michael Hirohama wrote:
>When prebuilt binary distributions are built, your recommended
>policy may be highly preferred. Do this when building and packaging
>for distribution but don't force this policy into the main CVS tree.
There are two motivating factors in the current practice.
1) Up to a few months ago, ht://Dig built a static db library and linked it in.
2) The APIs *do* change and when they do, it's obviously preferred to
stay with the latest version.
On the other hand, a large portion of the CVS tree, the package, and
diffs are taken up by the db code. So I would suggest that
*eventually* the db directory will be removed from the ht://Dig
source.
As for the notation that the current CVS version is old, there are
two reasons for this:
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. ;-)
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
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.
