Le Sat, Jun 12, 2010 at 12:35:41PM -0700, Russ Allbery a écrit : > > Despite its age, this bug is rather straightforward and is something we > really should have fixed years ago. The current wording around locations > of CGI programs implies that subdirectories of /usr/lib/cgi-bin may not be > used, but of course this is very widely used in packages already in the > archive and works with a typical web server configuration. Here is a > patch that explicitly allows this.
Hi all, will web servers find the CGI scripts automagically in /usr/lib/cgi-bin/<package>? If not, there is not much advantage to move them under /usr/lib as it is done now. Most other parts for packaged web sites are already in /usr/share/<package>. For simple sites, having the CGIs in /usr/lib/cgi-bin/ makes the maintainer's task simpler as he does not have to write webserver configuration files, but for more complex packages, it sometimes makes the task harder, for instance when the CGI scripts need to be patched because relative links are broken by the move. There were discussions along those lines on debian-devel a couple of monthes ago. I suggest to seriously consider to drop the requirement to separate the CGI scripts from the other files of the packaged websites. Have a nice day, -- Charles Plessy Illkirch, France -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100613090312.gc16...@kunpuu.plessy.org