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

Re: ambiguity in the guidelines



On Thursday 06 July 2006 09:08, Ralf Corsepius wrote:
> All this (and the warning in rpmlint) does, is to add confusion. I
> prefer strict and clear guidelines.
>
> I.e. either
> 1) CHANGELOGNAME is a freeform string. You can stick anything into it
> you might find useful.
>
> 2) Mandate a text format for CHANGELOGNAME. No exceptions allowed.

There is plenty of room between the 'do whatever you want' and 'YOU MUST DO 
EXACTLY AS WE SAY OR ELSE!!!' standpoints.

CHANGELOGNAME is somewhat freeform.  You can put as little or as much as you 
want.  Best practices would have you put your name, email address, and 
optionally the version-release associated with this changelog.  You could 
also put that version-release within the changelog entry rather than on the 
CHANGELOGNAME line.  This is up to the packager's discretion.

There, now we have something of 1, but with some suggested formatting.  Much 
nicer and much easier to swallow than a 400lb gorilla with a boulder and a 
bad attitude standing over you telling you how you must make a changelog 
entry.

Reviewers can suggest that the packager follow the best practice, but in the 
end it would be up to the packager on this issue.

-- 
Jesse Keating
Release Engineer: Fedora

Attachment: pgpK5bCOEN4oV.pgp
Description: PGP signature


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