Hello List,
Hi Robert,
I haven't looked at the code in depth, so I don't know how hard it would be to implement a config file option that would switch off that new behaviour, making 3.2.0b6 behave exactly like 3.1.6?
Unfortunately it is not that easy. The database structure is very different and it is not so easy to adapt it. I believe that it needs less time and work to work on optimisation than porting forward the 3.1.x code and allow a run-time different behaviour.
Would that be worth a try (it could save me from packaging two different versions for Sarge release)?
Don't take me wrong. Having seen the progress of the code, I think it is easier and faster to produce two different packages, maybe htdig and htdig31.
Ciao and thanks a lot for your contribution!
-Gabriele
--
Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check maintainer
Current Location: Prato, Toscana, Italia
[EMAIL PROTECTED] | http://www.prato.linux.it/~gbartolini | ICQ#129221447
> "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The Inferno
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev
