It's more useful to track changes by including a 
changelog file than adding a single string to the 
command line. 
 
A changelog file should be formatted to included 
without change into an rpm specfile -- and may 
contain one or more entries, constituting the history 
of the package.  This gets dumped into the %changelog 
section of the intermediate spec-file. 
 
For example; a file called ChangeLog could have the 
following contents, which would then be propogated to 
the actual rpm by adding --changelog=ChangeLog to the 
command line. 
 
* Wed 17 Sep 2003 Tony Campbell 
<tcampbell@users.sourceforge.net> 
- ported to ppc 
- another message 
 
* Tue Aug 19 2003 Tony Campbell 
<tcampbell@users.sourceforge.net> 
- Created 
 

Thanks for the report Tony. Sorry for the late reply, I tried to review a lot of distutils bugs some months ago but didn’t manage to read all of them. I’m assigning this to the distutils maintainer. Distutils is mainly frozen now, since we’ve seen that even changing undocumented internals may break third-party tools replying on them. New work happens in distutils2, where rpm-related code has been removed, because platform-specific tools are in a better position to comply with platform-specific oddities and policies.

Tarek, can this feature make it into distutils or does the freeze apply?

The feature freeze does apply.  Tarek has started a standalone project to build RPMs; I suggest you transfer this bug to https://bitbucket.org/tarek/pypi2rpm/

Happy hacking!