From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian J. Murrell Date: Mon, 05 Oct 2009 09:44:51 -0400 Subject: [Lustre-devel] Lustre version number and rpm "Release" In-Reply-To: <4AC69C7B.2020201@llnl.gov> References: <4AC56205.5060403@llnl.gov> <1254491700.26203.251.camel@pc.interlinx.bc.ca> <4AC69C7B.2020201@llnl.gov> Message-ID: <1254750291.22120.12.camel@pc.interlinx.bc.ca> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lustre-devel@lists.lustre.org On Fri, 2009-10-02 at 17:36 -0700, Christopher J. Morrone wrote: > > 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. Yes, that's true. > So really, we'll want an > additional "release_prefix" rpm variable. That would be a trivial patch. Feel free to open a bug and submit it. I can't see any reason why we'd not land that. > 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. Yes, I think you are correct about that. FWIW, (I think[1]) I'd like us (Sun) to get out of the business of putting anything meaningful in the Release tag and leave that for distributors to use. I'm not sure if or how that might help you though. b. [1] I've not really investigated the possibility yet, so it's really just a seed of an idea. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: