Hi Ted, I'm sorry, this isn't making any sense to me.
As I understand it, the path to the config file is compiled in to htsearch as a security precaution, so that when you specify which config file to use as a parameter when invoking htsearch from the webpage you are not exposing the directory location of ht://dig. Why do you feel that compiling in the location of the conf files is a drawback? I personally feel that adding an additional perl script is creating an unnecessary step in the processing of form data to htsearch, for the sake of convenience. I would assume that all ht://dig users are webmasters of some degree, and compiling htsearch with the location of the conf files shouldn't be a major task for most ht://dig users. Not to mention the issues faced by users who would then need to reconfigure their implementations of ht://dig in order to incorporate the new script. Kind regards, Rupert Jones -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Stresen-Reuter Sent: 03 June 2004 23:55 To: //Dig - Dev Subject: [htdig-dev] htsearch => wrapper script 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 -- Incoming mail is certified Virus Free. Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.245 / Virus Database: 263.1.1 - Release Date: 06/06/2004 -- Outgoing mail is certified Virus Free. Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.245 / Virus Database: 263.1.1 - Release Date: 06/06/2004 ------------------------------------------------------- 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
