I haven't posted these for a while since debian-policy has been quiet
lately. This version has had all proposals that were added to the
recent update of policy removed.
Note: for details of the policy process, see
http://www.debian.org/~srivasta/policy/ch3.html. Also, this summary is
available on
Goswin Brederlow schrieb am Dienstag, den 23. November 1999:
> Policy says that any binary must come with a manpage. I would like
> to have the same for packages.
I'm not sure, whether such a general rule is acceptable. Think for
example about the long list of libstdc++* packages: Should we wri
On Tue, Nov 23, 1999 at 06:00:32AM -0800, Chris Waters wrote:
> Anthony Towns writes:
> > Wichert, Chris, did this or my previous mail answer your objections,
> > or...?
> You yourself admitted that this is more of an explanatory thing than
> actual policy (after all, the bug in bash is a bug with
Goswin Brederlow <[EMAIL PROTECTED]> writes:
> Policy says that any binary must come with a manpage. I would like to have
> the same for packages.
I think I disagree. What section would be appropriate?
I think people are becoming too ready to propose grand, sweeping
changes to policy in order t
On Tue, Nov 23, 1999 at 02:54:56PM +, Julian Gilbey wrote:
> On Tue, Nov 23, 1999 at 11:02:24PM +1000, Anthony Towns wrote:
> > close 50832
> > reopen 50832
>
> Huh?!
Amendment
[...]
DD/MM/YYY] ...". Actually it might be better to close the
proposal and reop
Anthony Towns writes:
> Wichert, Chris, did this or my previous mail answer your objections,
> or...?
Well, you did a good job of explaining, and I have a better idea of
what you're *trying* to do now, but I'm still not sure this is the
right way.
You yourself admitted that this is more of an e
On Tue, Nov 23, 1999 at 04:34:59AM -0700, Ivan E. Moore II wrote:
> > > The package does follow policy in this manner.
> >
> > no it doesn't. in fact, imp is breaking policy because
> > /etc/imp/defaults.php3 is not in the package and therefore does not
> > belong to imp.
>
> ok...I never looked a
Previously Ben Collins wrote:
> How about someone write a script that pulls all of the packages and if
> there isn't a man page matching the package name, create one using the
> package's description as the content. Call it "update-packageman" or
> something.
shellutils contains a funky script tha
8 matches
Mail list logo
