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

Re: Working on debian developer's reference and "best packaging practices"



On Fri, May 03, 2002 at 09:34:58PM +1000, Anthony Towns wrote:
> On Thu, May 02, 2002 at 10:09:11AM +0100, Julian Gilbey wrote:
> > Part I: The Debian Archive
> >  1: DFSG and the sections of the archive (free, non-free, contrib, non-us)
>                    ^^^^^^^^
> 
> "Components" is a much better word to use here. (And is the word used
> everywhere but -policy, just about)

Fine.

> >  2: The different distributions (stable, etc.)
> 
> I.2 is probably more properly done in the developer's reference, since
> it doesn't impact how you go about constructing an ideal Debian package.

It affects how you write the changelog entry.  So maybe it should go
in both.

> Priorities? Sections?

Yes, of course.

> > Part II: Packages and metadata
[...]

> changelogs? copyright files?

Of course.

> Perhaps something like:
> [...]
> ...would work out well?

Maybe.  Definately worth considering.

> > Then each section could either have the structure:
> >   Policy dictate s
> >   Discussion, useful information, guidelines, examples
> > or we could merge them, and have policy dictates all in the form MUST,
> > SHOULD, MAY, MUST NOT, etc., as in the RFCs. 
> 
> I'm quite confident that trying to differentiate between requirements
> and guidelines like this will turn out to be completely unhelpful and
> a large waste of time, personally.

Don't RFCs do this frequently?  And I've never heard people making
such a complaint about them.

> > (As far as RC issues
> > goes, this could be marked by (RC) after the MUST/SHOULD/whatever,
> > with a catchall at the start of policy that the final decision on what
> > is RC rests with the release manager.)
> 
> As far as RC issues go, they'll be specified in an entirely separate
> document, not maintained by the policy group.

Do you really expect bug submitters to consult yet another document,
or is it just so that you can point people to it and say "See, this is
not considered an RC bug!"?  (I have no objection to there being
another document per se or to the policy group not being in control of
the list of RC issues.)

   Julian

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
              website: http://www.maths.qmul.ac.uk/~jdg/
   Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/
     Visit http://www.thehungersite.com/ to help feed the hungry


-- 
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: