Re: Wcal packaging question
On Wed, Jan 23, 2002 at 01:58:41PM -0600, Gunnar Wolf wrote: Hi, Debian policy states that the directory for CGI content should be /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and install in it. Thanks, I'll see how I can do that (the installer installs the cgi's and the images in $html_dir, so I guess I'll have to split $html_dir in the installer in a cgi and an images section... You should not need to modify Apache configuration - This directory is already scrpiptaliased in a default Debian installation. I know, I only had to change it because the cgi's were installed in /var/www/wcal... Always, if possible, avoid messing with other programs. If you have to... Well, then do it ;-) but I would recommend you not to. Greetings, Thanks for the advice! Wouter Hi, First of all: I am not an official debian developer. I'm packaging Wcal (a web-based calender/planner). It is by no means an official deb, but I want to do it as good as possible. I have some questions though: The Wcal installer asks me for the HTML directory for wcal. This is the directory that holds the CGI scripts and images (according to INSTALL). I currently use /var/www/wcal for this, but I doubt it is the right place for it. (I wouldn't like packages installing stuff in /var/www anyhow...). Can anybody give some advice on this? Another thing is the apache config: it must be edited before one can use wcal: I added the following: Directory /var/www/wcal AddHandler cgi-script .cgi DirectoryIndex index.cgi Options +ExecCGI /Directory How should I do this in the postinstall? Will it be overwritten when there's an apache update? I currently put this in README.Debian, and ask the user to it him/herself. Thanks in advance, hope this is the right place to ask this kind of questions... Wouter -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 +--- |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 +-- -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels.
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 10:42:59AM -0800, John H. Robinson, IV wrote: On Wed, Jan 23, 2002 at 07:04:25PM +0100, Wouter Eerdekens wrote: Another thing is the apache config: it must be edited before one can use wcal: I added the following: there are other webservers besides apache. like boa. I know, but the READE/INSTALL (I don't know which at the moment, I'm on a different machine) only talks about apache, I only use apache, and at the moment, the only people I know using the deb all use apache. I'm creating this package to master the art of packaging, and I have no idea how to automate the updating of the apache configuration cleanly, let alone how to do this for every webserver... (But the deb alreade depends on httpd, not on apache :) ... ) is there a generic handler to add the cgi information to the webserver backends? i am not aware of any. i doubt that wcal is so closely welded to the apache webserver that it cannot work with any of the other webservers available. i have no solutions for you, but i do want to bring up the awareness issue: there is more than one httpd. -john i count a dozen in sid: % grep-available --count -F Provides httpd 12 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wcal packaging question
Hi, Debian policy states that the directory for CGI content should be /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and install in it. You should not need to modify Apache configuration - This directory is already scrpiptaliased in a default Debian installation. Always, if possible, avoid messing with other programs. If you have to... Well, then do it ;-) but I would recommend you not to. Greetings, Hi, First of all: I am not an official debian developer. I'm packaging Wcal (a web-based calender/planner). It is by no means an official deb, but I want to do it as good as possible. I have some questions though: The Wcal installer asks me for the HTML directory for wcal. This is the directory that holds the CGI scripts and images (according to INSTALL). I currently use /var/www/wcal for this, but I doubt it is the right place for it. (I wouldn't like packages installing stuff in /var/www anyhow...). Can anybody give some advice on this? Another thing is the apache config: it must be edited before one can use wcal: I added the following: Directory /var/www/wcal AddHandler cgi-script .cgi DirectoryIndex index.cgi Options +ExecCGI /Directory How should I do this in the postinstall? Will it be overwritten when there's an apache update? I currently put this in README.Debian, and ask the user to it him/herself. Thanks in advance, hope this is the right place to ask this kind of questions... Wouter -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 +--- |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 +-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 01:58:41PM -0600, Gunnar Wolf wrote: Hi, Debian policy states that the directory for CGI content should be /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and install in it. Thanks, I'll see how I can do that (the installer installs the cgi's and the images in $html_dir, so I guess I'll have to split $html_dir in the installer in a cgi and an images section... You should not need to modify Apache configuration - This directory is already scrpiptaliased in a default Debian installation. I know, I only had to change it because the cgi's were installed in /var/www/wcal... Always, if possible, avoid messing with other programs. If you have to... Well, then do it ;-) but I would recommend you not to. Greetings, Thanks for the advice! Wouter Hi, First of all: I am not an official debian developer. I'm packaging Wcal (a web-based calender/planner). It is by no means an official deb, but I want to do it as good as possible. I have some questions though: The Wcal installer asks me for the HTML directory for wcal. This is the directory that holds the CGI scripts and images (according to INSTALL). I currently use /var/www/wcal for this, but I doubt it is the right place for it. (I wouldn't like packages installing stuff in /var/www anyhow...). Can anybody give some advice on this? Another thing is the apache config: it must be edited before one can use wcal: I added the following: Directory /var/www/wcal AddHandler cgi-script .cgi DirectoryIndex index.cgi Options +ExecCGI /Directory How should I do this in the postinstall? Will it be overwritten when there's an apache update? I currently put this in README.Debian, and ask the user to it him/herself. Thanks in advance, hope this is the right place to ask this kind of questions... Wouter -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 +--- |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 +-- -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Wcal packaging question
Hi, First of all: I am not an official debian developer. I'm packaging Wcal (a web-based calender/planner). It is by no means an official deb, but I want to do it as good as possible. I have some questions though: The Wcal installer asks me for the HTML directory for wcal. This is the directory that holds the CGI scripts and images (according to INSTALL). I currently use /var/www/wcal for this, but I doubt it is the right place for it. (I wouldn't like packages installing stuff in /var/www anyhow...). Can anybody give some advice on this? Another thing is the apache config: it must be edited before one can use wcal: I added the following: Directory /var/www/wcal AddHandler cgi-script .cgi DirectoryIndex index.cgi Options +ExecCGI /Directory How should I do this in the postinstall? Will it be overwritten when there's an apache update? I currently put this in README.Debian, and ask the user to it him/herself. Thanks in advance, hope this is the right place to ask this kind of questions... Wouter -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels.
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 07:04:25PM +0100, Wouter Eerdekens wrote: Another thing is the apache config: it must be edited before one can use wcal: I added the following: there are other webservers besides apache. like boa. is there a generic handler to add the cgi information to the webserver backends? i am not aware of any. i doubt that wcal is so closely welded to the apache webserver that it cannot work with any of the other webservers available. i have no solutions for you, but i do want to bring up the awareness issue: there is more than one httpd. -john i count a dozen in sid: % grep-available --count -F Provides httpd 12
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 10:42:59AM -0800, John H. Robinson, IV wrote: On Wed, Jan 23, 2002 at 07:04:25PM +0100, Wouter Eerdekens wrote: Another thing is the apache config: it must be edited before one can use wcal: I added the following: there are other webservers besides apache. like boa. I know, but the READE/INSTALL (I don't know which at the moment, I'm on a different machine) only talks about apache, I only use apache, and at the moment, the only people I know using the deb all use apache. I'm creating this package to master the art of packaging, and I have no idea how to automate the updating of the apache configuration cleanly, let alone how to do this for every webserver... (But the deb alreade depends on httpd, not on apache :) ... ) is there a generic handler to add the cgi information to the webserver backends? i am not aware of any. i doubt that wcal is so closely welded to the apache webserver that it cannot work with any of the other webservers available. i have no solutions for you, but i do want to bring up the awareness issue: there is more than one httpd. -john i count a dozen in sid: % grep-available --count -F Provides httpd 12 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels.
Re: Wcal packaging question
Hi, Debian policy states that the directory for CGI content should be /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and install in it. You should not need to modify Apache configuration - This directory is already scrpiptaliased in a default Debian installation. Always, if possible, avoid messing with other programs. If you have to... Well, then do it ;-) but I would recommend you not to. Greetings, Hi, First of all: I am not an official debian developer. I'm packaging Wcal (a web-based calender/planner). It is by no means an official deb, but I want to do it as good as possible. I have some questions though: The Wcal installer asks me for the HTML directory for wcal. This is the directory that holds the CGI scripts and images (according to INSTALL). I currently use /var/www/wcal for this, but I doubt it is the right place for it. (I wouldn't like packages installing stuff in /var/www anyhow...). Can anybody give some advice on this? Another thing is the apache config: it must be edited before one can use wcal: I added the following: Directory /var/www/wcal AddHandler cgi-script .cgi DirectoryIndex index.cgi Options +ExecCGI /Directory How should I do this in the postinstall? Will it be overwritten when there's an apache update? I currently put this in README.Debian, and ask the user to it him/herself. Thanks in advance, hope this is the right place to ask this kind of questions... Wouter -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 +--- |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 +--
