All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre version number and rpm "Release"
Date: Fri, 02 Oct 2009 17:36:11 -0700	[thread overview]
Message-ID: <4AC69C7B.2020201@llnl.gov> (raw)
In-Reply-To: <1254491700.26203.251.camel@pc.interlinx.bc.ca>

Brian J. Murrell wrote:

>> $ rpm -qpi lustre-1.8.1.50-2.6.18_70chaos_200910011803.x86_64.rpm
>> Name        : lustre                       Relocations: (not relocatable)
>> Version     : 1.8.1.50                          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.

Chris

  reply	other threads:[~2009-10-03  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  2:14 [Lustre-devel] Lustre version number and rpm "Release" Christopher J. Morrone
2009-10-02 13:55 ` Brian J. Murrell
2009-10-03  0:36   ` Christopher J. Morrone [this message]
2009-10-05 13:44     ` Brian J. Murrell
2009-11-12  1:20       ` Mag Gam
2009-11-14  9:38         ` Christopher J. Walker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AC69C7B.2020201@llnl.gov \
    --to=morrone2@llnl.gov \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.