Re: Bug#42477: PROPOSED} delay the /usr/doc transition till after potato

1999-08-11 Thread Manoj Srivastava
Hi, >>"Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes: Santiago> If we followed this rule of "only object in extreme circumstances", Santiago> we could be drawing circles forever. See: On the contrary, if every one objected formally all the time we shall never resolve anything.

Re: Hard-coding release names in policy (was Re: [PROPOSED} delay the /usr/doc transition)

1999-08-11 Thread Manoj Srivastava
Hi, >>"Chris" == Chris Waters <[EMAIL PROTECTED]> writes: Chris> Sorry, I'm not saying the latter is an inherently bad thing to Chris> do, I'm saying that if that's our *only* option, then we may Chris> have a problem. I *do* think it's bad to have "this may be Chris> amended in the future" a

location of debian policy manuals in dwww

1999-08-11 Thread Ardo van Rangelrooij
Hi, I just wanted to read the Debian Policy Manual through dwww and was expecting it under 'Debian'. However, to my big surprise it's located under 'Programming'. I could be wrong but isn't this a somewhat wrong place. The same goes for the Debian Menu Guidelines. I'm not saying that every Debi

Bug#40766: Rewrite of "configuration files" section

1999-08-11 Thread Manoj Srivastava
Hi, >>"Kai" == Kai Henningsen <[EMAIL PROTECTED]> writes: >> They're now in the debian-policy package, as >> /usr/doc/debian-policy/proposal.* >> >> The wording is weird, because it is written as a proposal. Kai> Aah. It should maybe be copied to doc/package-developer Kai> (ftp.debian.org)

Bug#42432: debian-policy: Proposal for CTV for Draft for Proof of Concept for Draft for Proposal for Proposal for CTV for a CTV to decide on a proposal for a CTV for the CTV on whether or not we shoud have a CTV on the /usr/doc to /usr/share/doc transition now, or later.

1999-08-11 Thread Manoj Srivastava
Hi, >>"Raphael" == Raphael Hertzog <[EMAIL PROTECTED]> writes: Raphael> The only working solution I see is that we should have a group of Raphael> (known) developers that would decide in such difficult cases. Sounds like you are talking about something like a tech ctte. manoj

Re: er

1999-08-11 Thread Joey Hess
Package: debian-policy Chris Waters wrote: > Joey Hess <[EMAIL PROTECTED]> writes: > > > I'd rather have /usr/lib/package/exmaples, with > > /usr/share/doc/package/examples linking to it. > > Yes, that seems like the most appropriate way to deal with example > binaries. Lets hope, though, that

What would the tree look like? (was Re: er)

1999-08-11 Thread Jim Lynch
Hi, >From the description "arch dep goes in /usr/lib//examples with symlink to /usr/doc//examples ", I cannot visualize the tree. For one, how would one distinguish arch-indep stuff from the arch-specific? / | usr |

Re: er

1999-08-11 Thread Julian Gilbey
> Any examples (configurations, source files, whatever), should be > installed in a directory `/usr/share/doc//examples'. These > files should not be referenced by any program--they're there > for the benefit of the system administrator and users, as documentation > - only. > + only. Archit

Re: What would the tree look like? (was Re: er)

1999-08-11 Thread Julian Gilbey
> Hi, > > From the description "arch dep goes in /usr/lib//examples > with symlink to /usr/doc//examples ", > I cannot visualize the tree. For one, how would one distinguish > arch-indep stuff from the arch-specific? I presume (as I mentioned in my seconding of the proposal) that Joey means a sy