Martin Mitchell wrote:
> I support this, it makes good sense to keep the policy method, for backward
> compatibility, while innovating.
I don't think any of us are arguning against backwards compatability.
--
see shy jo
Raul Miller wrote:
> Policy should be rather broad in scope and concise in expression.
Amen.
--
see shy jo
[I've looked over the other messages in this thread, but this looks like
the best message for me to respond to.]
Joey Hess <[EMAIL PROTECTED]> wrote:
> The question is: What needs to be policy?
>
> Specifically, Manoj's point of view seems to be that as we develop
> programs that tie the system to
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> You can innovate all you want -- as long as the old method in
> policy is supported (which you say you support). But you can't report
> bugs against packages for using the old method -- until you pass the
> new method (after it stabilizes) th
> > > 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
> > >
On Fri, Jan 22, 1999 at 09:17:17PM -0500, Brian White wrote:
> > > What will break most is packages that use /usr/lib/cgi-bin, and they can
> > > be fixed before the next release of Debian so as to make the entire
> > > transition appear seamless.
> >
> > Sure, the scripts will move and they will s
> > What will break most is packages that use /usr/lib/cgi-bin, and they can
> > be fixed before the next release of Debian so as to make the entire
> > transition appear seamless.
>
> Sure, the scripts will move and they will still work in and of
> themselves, but what about all the hard links fr
On Fri, Jan 22, 1999 at 07:35:55PM -0500, Brian White wrote:
> I really doubt that it will break "a lot" of systems...
>
> What will break most is packages that use /usr/lib/cgi-bin, and they can
> be fixed before the next release of Debian so as to make the entire
> transition appear seamless.
Su
[Aiie, what a huge followup list]
On Fri, 22 Jan 1999, Brian White wrote:
> Serious web hosts have probably already changed /cgi-bin/ to point to the
> correct place, thus abandoning the Debian scripts. These people will not
> be affected since we're only changing our system to match what they'
> I don't see this pertaining to cgi's. With the /usr/local convention it
> doesn't require any extra effort to use the programs (just add
> /usr/local/bin to PATH) but with a cgi-bin/cgi-lib seperation you will
> have to make two distinct calls to different URL's in order to call Debian
> cgi's an
10 matches
Mail list logo
