> On Thu, Nov 02, 2000 at 09:16:02AM -0500, Brian White wrote:
> > -----
> > Most people setting up a web site expect /cgi-bin/ to be available for
> > scripts on their site. Unfortunately, Debian uses this for those scripts
> > packages that get installed. These two need to be independant.
> >
> > As such, Debian's system needs to be altered a bit. I recommend using
> > instead the name "/cgi-lib/" for scripts under /usr/lib/cgi-bin/. This
> > will keep both features independant and not affect the general use of
> > the system.
> > -----
>
> This seems sensible to me, could you give a patch to policy that
> can be actually included?
Sure. Here's what I wrote up as a patch to "policy.sgml".
===============================================================================
--- policy.sgml.orig Fri Nov 3 00:02:17 2000
+++ policy.sgml Fri Nov 3 00:18:45 2000
@@ -2949,9 +2949,20 @@
</example>
and can be referred to as
<example>
- http://localhost/cgi-bin/<cgi-bin-name>
- </example></p></item>
+ http://localhost/cgi-lib/<cgi-bin-name>
+ </example></p>
+ <p>The purpose of using <tt>cgi-lib</tt> instead of
+ <tt>cgi-bin</tt> is that most webmasters are used to having
+ <tt>cgi-bin</tt> available for their own local use, much like
+ <tt>/usr/local</tt>. Having packages use <tt>cgi-lib</tt>
+ means that no changes need to be made by the webmaster to both
+ keep what they are used to and still have access to Debian
+ packages.</p>
+
+ <p>Web servers should include <tt>/cgi-lib/</tt> as a standard
+ ScriptAlias of <tt>/usr/lib/cgi-bin/</tt>.</p></item>
+
<item><p>Access to html documents</p>
===============================================================================
Brian
( [EMAIL PROTECTED] )
-------------------------------------------------------------------------------
A hundred years from now it will not matter what my bank account was, the
sort of house I lived in, or the kind of can I drove... But the world may
be different because I was important in the life of a child.
