Mailinglist Archive: opensuse-packaging (135 mails)
| < Previous | Next > |
Re: [opensuse-packaging] Re: kernel-*.spec fixed strings are no fun
- From: James Oakley <jfunk@xxxxxxxxxxxxxx>
- Date: Mon, 13 Aug 2007 12:58:12 -0300
- Message-id: <200708131258.12670.jfunk@xxxxxxxxxxxxxx>
On Friday 10 August 2007 1:21 pm, Jan Blunck wrote:
> On Thu, 09 Aug 2007 21:34:31 +0200, Jan Engelhardt wrote:
> > the kernel-*.spec files contain a lot of hardcoded strings, such as
> > 2.6.22.1 for what's currently cooking. This causes a major pain when
> > trying to bump the version by oneself. All occurrences need to be
> > replaced by more-or-less blunt scripts (simple perl -pe 's///'), since
> > the .in files are not available. If these could please be added to the
> > kernel-source pack, that would greatly simplify work.
>
> Well, most of the scripts need direct access to our internal CVS server.
> So just putting them somewhere doesn't help. Although this is something I
> already have on my to-do list.
I ended up writing my own script to build kernel spec files from templates,
which I have attached.
Basically, I made 3 spec templates from the specs I found in the buildservice,
using @@VARIABLENAME@@ where I wanted substitutions:
kernel-source.spec.in
kernel-binary.spec.in
kernel-syms.spec.in
Then I created a bunch of files containing flavor-specific variables:
kernel-bigsmp.vars
kernel-debug.vars
kernel-default.vars
kernel-kdump.vars
kernel-ppc64.vars
kernel-s390.vars
kernel-um.vars
kernel-vanilla.vars
kernel-xenpae.vars
kernel-xen.vars
Here's the contents of kernel-bigsmp.vars, for example:
FLAVOR="bigsmp"
EXCLUSIVEARCHES="%ix86"
SUMMARY="Kernel with PAE Support"
DESCRIPTION="This kernel supports up to 64GB of main memory. It requires
Physical\n\
Addressing Extensions (PAE), which were introduced with the Pentium Pro\n\
processor."
Hope that helps,
--
James Oakley
jfunk@xxxxxxxxxxxxxx
> On Thu, 09 Aug 2007 21:34:31 +0200, Jan Engelhardt wrote:
> > the kernel-*.spec files contain a lot of hardcoded strings, such as
> > 2.6.22.1 for what's currently cooking. This causes a major pain when
> > trying to bump the version by oneself. All occurrences need to be
> > replaced by more-or-less blunt scripts (simple perl -pe 's///'), since
> > the .in files are not available. If these could please be added to the
> > kernel-source pack, that would greatly simplify work.
>
> Well, most of the scripts need direct access to our internal CVS server.
> So just putting them somewhere doesn't help. Although this is something I
> already have on my to-do list.
I ended up writing my own script to build kernel spec files from templates,
which I have attached.
Basically, I made 3 spec templates from the specs I found in the buildservice,
using @@VARIABLENAME@@ where I wanted substitutions:
kernel-source.spec.in
kernel-binary.spec.in
kernel-syms.spec.in
Then I created a bunch of files containing flavor-specific variables:
kernel-bigsmp.vars
kernel-debug.vars
kernel-default.vars
kernel-kdump.vars
kernel-ppc64.vars
kernel-s390.vars
kernel-um.vars
kernel-vanilla.vars
kernel-xenpae.vars
kernel-xen.vars
Here's the contents of kernel-bigsmp.vars, for example:
FLAVOR="bigsmp"
EXCLUSIVEARCHES="%ix86"
SUMMARY="Kernel with PAE Support"
DESCRIPTION="This kernel supports up to 64GB of main memory. It requires
Physical\n\
Addressing Extensions (PAE), which were introduced with the Pentium Pro\n\
processor."
Hope that helps,
--
James Oakley
jfunk@xxxxxxxxxxxxxx
| < Previous | Next > |