On Fri, Aug 17, 2007 at 08:58:20AM +0200, Dirk Stoecker wrote:
Of course it can make total sense to derive the rpm changelog automatically from the commit log, in certain cases -- I agree on that.
You are right. Nevertheless I'm too lazy to change my RPM packages (especially as I hate the syntax). But I'm used to have -m due to svn and cvs.
Probably the solution could be a tag system like the one used in KDE. Adding e.g. "CHANGELOG:" to the commit message to have it in the RPM changelog?
No, I don't think that this is a good idea. An overkill mechanism IMO, and it'd only make sense if you work exactly in the way and order you assume here...
Would be very helpful I think.
And when having Tags, we could also implement "NOREBUILD" to prevent a rebuild e.g. when checking in new files and before I had the chance to edit the .spec.
Doesn't make sense to me. The basic idea does, but that should rather be an optional query argument sent to the api IMO, not a "magic" part of the changelog. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development