From: Christopher J. Walker <C.J.Walker@qmul.ac.uk>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre version number and rpm "Release"
Date: Sat, 14 Nov 2009 09:38:19 +0000 [thread overview]
Message-ID: <4AFE7A8B.9070006@qmul.ac.uk> (raw)
In-Reply-To: <1cbd6f830911111720p1b6d9e54ibb5410709b38176f@mail.gmail.com>
Mag Gam wrote:
> Just curious, why do people build their own releases if everything is
> available in release RPMs. Do most people or organizations build their
> own version of Lustre or do they use the RPMs?
>
We need to keep up to date with the latest kernel security errata - so
I've been building Lustre clients.
> I am asking because I would like to build my own version and wanted to
> see the benefits of it.
Knowing that you can, even if you don't currently need to, is an advantage.
> TIA
>
> 2009/10/5 Brian J. Murrell <Brian.Murrell@sun.com>:
>> 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.
>>
>> _______________________________________________
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-devel
>>
>>
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
prev parent reply other threads:[~2009-11-14 9:38 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
2009-10-05 13:44 ` Brian J. Murrell
2009-11-12 1:20 ` Mag Gam
2009-11-14 9:38 ` Christopher J. Walker [this message]
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=4AFE7A8B.9070006@qmul.ac.uk \
--to=c.j.walker@qmul.ac.uk \
--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.