Bug#32263: Unexpected use of /cgi-bin/

[Brian White <bcwhite@pobox.com>]

> > 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.
> 
> I don't seem to understand your intention.  Why to you want to separate
> the /cgi-bin/ directory Debian uses for scripts from the une the webmaster
> uses?  They fit together just fine.

I don't want a separate directory for Debian to use.  I would like the
standard directory available for the webmaster to use.  Think of
/cgi-lib/ as an equivalent to /usr/lib/ or /usr/bin/, and /cgi-bin/ as
an equivalent to /usr/local/bin/.


> > 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.
> 
> If you file this as bug agains Apache you need to file it against all other
> httpd's that support cgi-bin as well.  Thus I assume that you need to modify
> policy first.

I figured I'd start with the big one and then work my way around.  However,
somebody has reassign the bug to debian-policy since it is official Debian
policy to do it the way it is.  I wish somebody had told me that when I
originally sent mail around asking for opinions about this idea.

                                          Brian
                                  ( bcwhite@pobox.com )

-------------------------------------------------------------------------------
      Management should work for the engineers, not the other way around.