Re: Bug#167513: the lack of consultation or discussion regarding this change is not good

> Debian has survived the transition of /usr/doc to /usr/share/doc, which
> took a long time to do.  This one can't be worse.  But I also agree with
> those who don't want to just change the default config: there's no point
> breaking everybody's installations.

Absolutely.  That was one thing I wanted to guarantee in my policy.  We
cannot break existing configs.  By simply adding a second alias and not
changing the existing one if it exists, this is accomplished.


> My only strong argument against my own suggestion here is that some
> sites - mine, for example - override the default /cgi-bin/ in each vhost
> container.  Moving to /cgi-lib/ in the default config would expose the
> system's /usr/lib/cgi-bin/ in each vhost.  This may not be desirable.
> I'm sure you can throw in some debconf warnings though.

This is a good point.  My sites run the same way.  It should be easy for
an admin to remove /cgi-lib/ in much the same way they could currently
remove /cgi-bin/ just by commenting it out.

Overall, though...  If admins aren't currently using /cgi-bin/ for system
scripts then a newly added /cgi-lib/ alias will have minimal impact since
that admin won't have installed the packages that provide system scripts.

                                          Brian
                                  ( bcwhite@xxxxxxxxx )

-------------------------------------------------------------------------------
  Generated by Signify v1.10.  For this and more, visit http://www.debian.org/