Bug#32263: Splitting CGI-BIN

[Brian White <bcwhite@pobox.com>]

> >       Have we decided on whether aj's proposed changes (below) are
> >  what we reached a consensus on?
> > ======================================================================
> >          /usr/lib/cgi-bin/
> >                  <packages dump CGI scripts in here willy-nilly>
> >          ~wwwdata/cgi-bin/
> >                  <packages make symlinks to /usr/lib/cgi-bin/blah in postinst,
> >                   based on some setting in /etc/ somewhere>
> >  So that admins can just rm symlinks to scripts they don't need, or,
> >  if they want to be absolutely sure they don't get any cgi-bin scripts
> >  they don't want, change the config file.
> > ======================================================================
> >       Hmm. What happens if I remove a symlink, and then the package
> >  is upgraded?

I don't believe this to be necessary.  As long as webservers don't
change existing <webroot>/cgi-bin aliases (use the new default only
for new installations), then there won't be any difficulties.  An
advanced webmaster will either not install said packages or will
alias <webroot>/cgi-lib as he/she sees fit.

I think making symlinks will be a pain for package maintainers, prone
to error (especially for configs with multiple virtual hosts), and give
no real benefit.

I would really like to keep this simple.

                                          Brian
                                  ( bcwhite@pobox.com )

-------------------------------------------------------------------------------
          Until we are first independent, we cannot be interdependent.