On 09/07/2011 12:42 PM, Josh Boyer wrote:
On Wed, Sep 7, 2011 at 12:32 PM, Genes
MailLists<lists(a)sapience.com> wrote:
> On 09/07/2011 09:57 AM, Josh Boyer wrote:
>
>
>>
>> %changelog isn't for developers. It's for users to see what the
>> developers changed in the package.
>>
>
> Would a git-shortlog suffice for %changelog ? Assuming appropriate
> comments are required for fedora's git repo.
No... users can access %changelog for the RPMs on their system via
rpm. Making them go to a git repository elsewhere to figure out what
changed isn't exactly friendly.
Unless of course you meant "have fedpkg automatically stick a
git-shortlog into the %changelog section of the spec file on commit"
or something. Then.. maybe.
The installer team has been doing this for anaconda for a while now.
The RPM changelog block is automatically generated for us when we make a
new release.
When we do a "make release", this script (among other things) is run:
http://git.fedorahosted.org/git/?p=anaconda.git;a=blob_plain;f=scripts/ma...
And we have a commit log format we follow:
http://git.fedorahosted.org/git/?p=anaconda.git;a=blob_plain;f=docs/commi...
It works well for us.
And yes, this assumes in all cases that developers are actually
putting useful information in both %changelog and commit logs.
--
David Cantrell <dcantrell(a)redhat.com>
Supervisor, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT