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

[Brian White <bcwhite@pobox.com>]

> > > Sure, the scripts will move and they will still work in and of
> > > themselves, but what about all the hard links from webpages on their
> > > site to scripts in /cgi-bin that are debian cgi scripts installed by
> > > packages. If we suddenly change it to /cgi-lib then links to all the
> > > debian installed cgi's are now broke.
> >
> > If it has been coded as this, fixing it is trivial...  Place symlinks
> > in the new /cgi-bin/ (assuming that isn't how it has already been done)
> > to the scripts in /usr/lib/cgi-bin.  You could even ask to do this
> > during the upgrade procedure of apache.
> 
> Polluting their 'new' local /cgi-bin with links to /cgi-lib kind of
> defeats the whole purpose doesn't it?

Yes.  That's why I suggested the upgrade could offer to do such.  An
intelligent upgrade script could even offer only if it detects a need.

                                          Brian
                                  ( bcwhite@pobox.com )

-------------------------------------------------------------------------------
   If you love something, set it free.  If it comes back, it was, and always
     will be yours.  If it never returns, it was never yours to begin with.