[Lustre-devel] Lustre version number and rpm "Release"

Christopher J. Morrone morrone2 at llnl.gov
Fri Oct 2 17:36:11 PDT 2009

Brian J. Murrell wrote:

>> $ rpm -qpi lustre-
>> Name        : lustre                       Relocations: (not relocatable)
>> Version     :                          Vendor: (none)
>> Release     : 2.6.18_70chaos_200910011803   Build Date: Thu Oct  1
> Then presumably the kernel you built against is 2.6.18_70chaos.  Is that
> correct?

That is correct.

> %{!?release: %define release @RELEASE@}
> That means you can define Release for your rpm build on the command line
> with:
> $ rpmbuild --define 'release whatever_you_want' ... lustre.spec

Well, that is true, except that we just want to prefix the release, not
replace it.  If we replace it with our own definition, we have to repeat
the kernel detection, and timestamp part.  So really, we'll want an
additional "release_prefix" rpm variable.

There is an additional wrinkle that I didn't mention.  Our automated
build system is designed to take source rpms and build the binary rpms
from that.  If we just set "release" at source rpm build time, I don't
think that it will be remember later when the binary rpms are built.

Part of the reason that our build farm works that way is that we would
like other users of our linux distribution to be able to easily rebuild
lustre (and any other kernel modules) from the source rpm.

In the end though, it looks like the most reasonable way to handle this
is to have our own spec file for the chaos linux distribution.


More information about the lustre-devel mailing list