Re: [PATCH for-xen-4.5] tools/mkrpm: improve version.release handling

[Olaf Hering <olaf@aepfle.de>]

On Tue, Nov 04, George Dunlap wrote:

> A number based on the time you happened to create the RPM, not based
> on something intrinsic about the content of the RPM; that just seems
> kind of hacky to me.  It happens to work well for your common
> workflow, but you can certainly imagine other workflows or other
> situations where you'd have to more manually override things anyway
> (for instance, doing bisections, or comparing functionality in
> different releases).  It seems like rather than having to remember
> when you can skip the manual override bits, and when you can't, it
> would be better to just use them all the time.

George, the release number is and was never meant to describe the
content of a package. It just means "its different". And it will even
work for bisect because the package is always "newer", even if the
content is different.

And after commit b8ebc6b9e07d3cc061fdded1a0530bd6b25d4634 ("tools/mkrpm:
allow custom rpm package name") and all the --prefix changes its easy to
have independent packages for every branch.

Olaf