Bug#102199: Next stage in usr/doc -> usr/share/doc transition

2001-06-26 Thread Joey Hess
Anthony Towns wrote: > I think the most efficient way of handling usr/doc for woody will be to > have everything reference /usr/share/doc, and require all packages to > put their files in /usr/share/doc, and to make symlinks in /usr/doc. The > latter is mainly for partial upgrades. > > To achieve

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Joey Hess
Anthony Towns wrote: > + The guidelines in this manual are expected to be interpreted > + intelligently, with a view to improving the technical quality > + of the Debian distribution. Where a guideline in this manual > + does not make sense for a particular pack

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Anthony Towns
On Tue, Jun 26, 2001 at 12:51:52AM -0400, Rene Weber wrote: > I am unclear as to the import of "should generally" in this context. Is > this a further diminished form of "should" (but stronger than "may")? I > believe Debian would be better served by framing this as a "must" (after > all, if

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Anthony Towns
On Tue, Jun 26, 2001 at 01:11:09AM -0400, Joey Hess wrote: > Anthony Towns wrote: > > + The guidelines in this manual are expected to be interpreted > > + intelligently, with a view to improving the technical quality > > + of the Debian distribution. Where a guideline in

Bug#102199: Next stage in usr/doc -> usr/share/doc transition

2001-06-26 Thread Anthony Towns
Your message was From: Joey Hess <[EMAIL PROTECTED]>, [EMAIL PROTECTED] ...? On Tue, Jun 26, 2001 at 02:02:17AM -0400, Joey Hess wrote: > Do you mean accessing docs programatically (rare) or by reference in man > pages and error messages (sorta common)? Programmatically, mainly. > If the latt

Bug#102199: Next stage in usr/doc -> usr/share/doc transition

2001-06-26 Thread Stephen Stafford
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 26 June 2001 7:02 am, Joey Hess wrote: > Anthony Towns wrote: > > Do you mean accessing docs programatically (rare) or by reference in > man pages and error messages (sorta common)? If the latter, it seems > a bit late to ask for a thuroug

Colo Servers, Telco-Grade Configuration, Embedded/Turnkey Systems

2001-06-26 Thread debbi
I have a question related to a variety of similar common server configurations. In many cases servers are remote; they have no console, or the console is almost always unattended. There are a number of settings that will make a system (even a PC) much more robust under these circumstances.

Bug#102199: Next stage in usr/doc -> usr/share/doc transition

2001-06-26 Thread Stephen Stafford
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 26 June 2001 10:42 am, Stephen Stafford wrote: > Well, if you want to write a script to find them all and it doesn't > turn out to be too large a number (somewhere under 50 would be 'not > too large' probably, depending on how fast freeze i

Re: Moving Policy to Docbook

2001-06-26 Thread Manoj Srivastava
>>"Julian" == Julian Gilbey <[EMAIL PROTECTED]> writes: Julian> I'm happy to add Chris's bug-fix and a couple of other small niceties Julian> for release 3.5.5.1 as long as Manoj is OK with that. Please go ahead. I'm holding off until after I get back from USENIX, and am looking into h

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Manoj Srivastava
Hi, >>"Anthony" == Anthony Towns writes: Anthony> +In rare cases a package may be enough of a special case that Anthony> +it should not follow a guideline and the exception would just Anthony> +be confusing if listed in this manual itself. Is this likely to be the case

Re: Moving Policy to Docbook

2001-06-26 Thread Michael Alan Dorman
Manoj Srivastava <[EMAIL PROTECTED]> writes: > Please go ahead. I'm holding off until after I get back from USENIX, > and am looking into how much work mastering XSLT and stylesheets is > goint to take. I'm willing to collaborate on this a bit if that would help. Mike.

Bug#102199: Next stage in usr/doc -> usr/share/doc transition

2001-06-26 Thread Joey Hess
Anthony Towns wrote: > Your message was > From: Joey Hess <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > ...? Hmm. > On Tue, Jun 26, 2001 at 02:02:17AM -0400, Joey Hess wrote: > > Do you mean accessing docs programatically (rare) or by reference in man > > pages and error messages (sorta common)? >

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Joey Hess
Anthony Towns wrote: > On Tue, Jun 26, 2001 at 01:11:09AM -0400, Joey Hess wrote: > > Anthony Towns wrote: > > > + The guidelines in this manual are expected to be interpreted > > > + intelligently, with a view to improving the technical quality > > > + of the Debian dist

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Colin Watson
Anthony Towns wrote: >On Tue, Jun 26, 2001 at 01:11:09AM -0400, Joey Hess wrote: >> Anthony Towns wrote: >> > + The guidelines in this manual are expected to be interpreted >> > + intelligently, with a view to improving the technical quality >> > + of the Debian distribu

Re: Policy proposal: Cpu extension code, update-ldsoconf

2001-06-26 Thread Camm Maguire
Greetings! Michel LESPINASSE <[EMAIL PROTECTED]> writes: > On Mon, Jun 25, 2001 at 03:16:27PM -0400, Camm Maguire wrote: > > Greetings! This is hardly formal, but it seems as though we don't > > have a policy on this yet, and a number of packages are appearing > > (e.g. atlas, gmp2) which can be

Re: Resolving policy and practice wrt sbin directories (traceroute)

2001-06-26 Thread Rene Weber
Hello, [This message is a reply to some of Anthony's text in bug #102213, where he notes that this discussion is not relevant to the bug.] On Tue, Jun 26, 2001 at 03:12:06PM +1000, Anthony Towns wrote: > That message of Herbert's was a criticism of the language in the FHS. For > example,

Bug#102213: PROPOSAL] Policy interpretation and exceptions

2001-06-26 Thread Rene Weber
Hello, On Tue, Jun 26, 2001 at 03:12:06PM +1000, Anthony Towns wrote: > Uh, no, it should definitely not be a "must". There is no way I'm going > to throw a package out of the distro because it fails to mention that > policy is stupid in some way or another. Ok, fair enough (although sure