> >> > The main reason why I asked was this: the Berkeley DB (in its various > versions) is already > present in the debian system. Dynamically linking against it coud shrink > the package. However, > If you feel those patches are important, I wont link against the libdb, > and use what you provide instead > (which will put me in an awkwards situation, but thats my problem)
Understandable. The other thing you could do is hack a makefile that would package up all of the htdig .so library files into one file, and link the binaries against that. Then you wouldn't have to install a BDB library that is non-standard. We should do this anyway at some point.. I don't see a reason in the world why we need so many seperate library files! It is also possible to disable the various page-compression configuration code in HtDig and link against a standard BDB 3.0.55 version. I wouldn't recommend this option unless you like wasting disk-space like a drunken sailor. > Since I maintain the package anyway (and need to do the manpages, for my > users to be content), > I'd be greatly honored to join the team in this functiom. Awesome. Neal Richter Knowledgebase Developer RightNow Technologies, Inc. Customer Service for Every Web Site Office: 406-522-1485 ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
