[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: should vs must



On Thu, Mar 01, 2001 at 11:14:58AM +0000, Julian Gilbey wrote:
> So we say "Packages MUST specify source dependencies." and in the
> annex to policy: "Failure to specify source dependencies is currently
> not RC."

If the MUST specify source dependencies, it's RC by definition. That was
the whole point of the MUST/SHOULD/MAY split.

If you want something else: either per-package exceptions, or some way
of documenting how policy is planned to look in the future (at least,
when there is such a plan), I've already suggested ways of dealing with
this: README.Debian and BLOCKED/ONHOLD. But MUST already serves a purpose
as is, please don't mess with it.

Cheers,
aj

-- 
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.

``_Any_ increase in interface difficulty, in exchange for a benefit you
  do not understand, cannot perceive, or don't care about, is too much.''
                      -- John S. Novak, III (The Humblest Man on the Net)

Attachment: pgpPiCoHnfCZq.pgp
Description: PGP signature


Reply to: