On Tue, Oct 09, 2001 at 01:35:06PM -0400, Joey Hess wrote:
> > > Or the package's name may
^^^
> > > be an abbreviated version, and the longer name put in the Provides
> > > field.
> >
> > Require is probably too strong, but I suggest this should instead read:
> >
> > or the package's name may be abbreviated. If the package does not
^^^
> > use the full name, it should include the full name in the Provides
^^^^^^
> > field.
>
> I have no problem with that wording, but I fail to see how it is any
> different from the original wording. My original wording doesn't say
> "and the longer name OPTIONALLY put in the Provides field", it says you
> can abbreviate the name AND put the longer name in the provides field.Actually it does say that, although I don't think you meant it that way. The original wording captures the Provides bit under a 'may' clause; I have moved it to a 'should' clause. Policy 1.1: In this manual, the words must, should and may, and the adjectives required, recommended and optional, are used to distinguish the significance of the various guidelines in this policy document. Packages that do not conform to the guidelines denoted by must (or required) will generally not be considered acceptable for the Debian distribution. Non-conformance with guidelines denoted by should (or recommended) will generally be considered a bug, but will not necessarily render a package unsuitable for distribution. Guidelines denoted by may (or optional) are truly optional and adherence is left to the maintainer's discretion. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : | Dept. of Computing, `. `' | Imperial College, `- http://www.debian.org/ | London, UK
pgplJISdPyqut.pgp
Description: PGP signature
