Re: [PROPOSED] Split /cgi-bin/ into system and local parts

[Brian White <bcwhite@pobox.com>]

> > As such, I think Debian's system should 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.
> >
> > More information about this as well as some potential problems and potential
> > solutions can be found in the history of this bug.
> >
> >       http://www.debian.org/Bugs/db/32/32263.html
> 
> I like this idea, but think that removing existing content from existing
> cgi-bin directories is a bad idea.

Unfortunately, I think you really have to.  Currently, cgi-bin is simply
mapped to /usr/lib/cgi-bin which means (since /usr is to be considered
read-only) than local admins can't add things under this standard location.
The best they can do is create their own directory and symlink everything
to that place.  This scheme will eventually fail as packages get added
and removed.

In the bug report, I proposed creating cgi-lib in /usr/lib/cgi-bin and
cgi-bin in ~www-data/cgi-bin.  Then, for compatibility with older packages,
symlink everything currently under cgi-lib to cgi-bin.  It's not perfect,
but would at least make the transition fairly smooth.


> After potato, I think it's fine to drop cgi-bin as a way to reference
> debian materials: but only on new systems or where the administrator
> manually intervenes.

I think it would be okay for a webserver installion script to detect the
old layout and prompt for "upgrade".

                                          Brian
                                  ( bcwhite@pobox.com )

-------------------------------------------------------------------------------
Seize the moment!  Live now.  Make "now" always the most important time. -- JLP