Re: [PATCH] Bug in scripts/package/mkspec?

[Patrick LeBoutillier]

Michal,

Maybe the easiest way is just to rebuild the spec file everytime we do
"make rpm".
I'll try it and see how it does.

Do you know of the .version file is used for anything outside of the
"make rpm" process?

Patrick


On Thu, Jan 6, 2011 at 7:54 AM, Michal Marek <mmarek@xxxxxxx> wrote:
> On Thu, Dec 02, 2010 at 04:15:20PM -0500, Patrick LeBoutillier wrote:
>> Hi Michal,
>>
>> Sorry for the bad patch. Here is basically what I do:
>>
>> $ make menuconfig
>> $ make rpm
>> ...
>> Wrote: /root/rpmbuild/RPMS/x86_64/kernel-2.6.36.1-1.x86_64.rpm
>> ...
>> $ make menuconfig # tweak some configs
>> $ make rpm
>> ...
>> Wrote: /root/rpmbuild/RPMS/x86_64/kernel-2.6.36.1-1.x86_64.rpm
>> ...
>>
>>
>> My expectation (and perhaps it is incorrect) is that subsequent "make
>> rpm"s on the same build tree
>> yield rpms with increasing release numbers (2.6.36.1-1, 2.6.36.1-2,
>> ...). Is this how it's supposed
>> to work?
>
> I see the problem now, unfortunatelly I haven't yet found a fix. The
> problem is that the .version file is updated during build, but rpm needs
> to know the release number in advance. The fact that there are about
> four places that deal with the .version file is also not helping :-(.
>
> Michal
>



-- 
=====================
Patrick LeBoutillier
Rosemère, Québec, Canada
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/