> >> Yes. But the scripts still live in ~www-data/cgi-bin, right?
> >> If not, I missed when you are going to have packages move the scripts
> >> out.
>
> Brian> All system scripts would live under /usr/lib/cgi-bin and be
> Brian> accessed via <webroot>/cgi-lib. To make for a smooth
> Brian> transition, any existing alias of <webroot>/cgi-bin would
> Brian> remain untouched thus allowing uninterrupted access until all
> Brian> of the packages that need to change can be changed. This
> Brian> shouldn't be a hardship for anybody since they're already
> Brian> forced to use <webroot>/cgi-bin in that capacity right now.
>
> So, as an early adopter, I start using /usr/lib/cgi-bin, it
> won't work until the web servers have done so. Hmm. perhaps we should
> recommend web servers provide the script alias, but warn packagers
> not to use it until web servers have transitioned.
By "I start using", you mean as a package maintainer? If so, then you
are correct. It's important that the webserver packages get updated first,
then we can get to the real goal converting packages to use cgi-lib so
that webmasters can set <webroot>/cgi-bin to be ~www-data/cgi-bin (or
whatever they prefer). Whew!
> Unless, of course, the web server maintainers agree to add the
> alias on their own, in advance of policy, since you convinced them of
> the wisdom of doing so (well, I can dream)
<laugh>
> >> I see two problems. The name space pollution has not been
> >> reduced -- since all scripts live in the same dir on disk; my
> >> cgi-file could be overwritten by a debian package. All we have done
> >> is created two names for the same underlying directory; but not given
> >> the sysadmin a private place to keep his files that is safe.
>
> Brian> Your personal cgi-script should _not_ be in /usr/lib/cgi-bin.
>
> I meant my packages cgi-bin script. I get kinda propreitary
> about _my_ code.
>
> Any how, when the web servers have mostly implemented the
> alias, we can then make general policy for packages to follow.
> Hmm. no way to avoid having all users change their book marks, then?
Yup. Good point, though; I hadn't thought of bookmarks. For the most part,
it won't make any difference. Most existing sites will not change the current
<webroot>/cgi-bin setting and thus both cgi-bin and cgi-lib will point to the
same place. Old bookmarks will still work. New installations will get the new
setting of <webroot>/cgi-bin but there won't be too many bookmarks to those
sites.
Brian
( [EMAIL PROTECTED] )
-------------------------------------------------------------------------------
BUFFERS=20 FILES=15 2nd down, 4th quarter, 5 yards to go!
