You know, in setting up my package, I realized that it seems like a real drawback to have to compile in the location of the conf files into htsearch (rather than having it look in it's own directory, for example, for cases in which the location is not compiled in).

Maybe, instead of putting htsearch in cgi-bin, we could put htsearch in --prefix/bin and drop a perl script into cgi-bin that simply passes the request on to htsearch (and htsearch sends the response). That way, we could keep all the htdig binaries together in one place.

Does this make sense to anyone else or just to me?

Ted Stresen-Reuter



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to