On Sat, Sep 21, 2002 at 12:11:47AM -0600, Vincent Danen wrote:
> 
> Yup, Ben's right.  Updates don't go into CVS... never have and I doubt 
> they ever will.  The only times that maintainers have anything to do 
> with updates is usually immediately after a release when there are 
> bugfixes... these get into CVS because they are typically rebuilds from 
> cooker. 
> Or when we do kernel updates because Juan does most of the 
> work there, but again, these don't go into CVS.

All of this would be solved (pertaining to the kernel specfile anyway)
by following my other suggestion: putting the specfile that builds a
release of kernels into the kernel-source package.

I have successfully made modifications to the 2.4.18-8.1mdk specfile
to allow you to package the kernel that was built in the kernel-source
(i.e.  /usr/src/linux-2.4.18-8.1mdk) directory.  So for instance you
can follow these steps:

# rpm -ivh kernel-source-...
# cd /usr/src/linux-...
<patch, make config, whatever else you want to do for your custom kernel>
# make dep; make clean; make bzImage; make modules
# rpm -bb -without binary

(-without binary is a lame option name; it needs more thought) and
then rpm will package up the kernel you just built into an RPM which
will operate exactly as if it was built right from source using the
Mandrake RPM (i.e. with all of the Mandrake scripts, etc.).

There are a couple of things missing still.  I want to be able to pass
a "flavour" (i.e. "-with flavour bjm" to produce
kernel-<version>-<serial>mdkflavour), and in fact force the
requirement that a flavour name be passed if "-without binary" is
used.  I dunno how to do that yet though.  Just need to check out
these new macros and value passing options in RPM.

I think this would be a very nice feature of the kernel-source package
for those that do need to build their own kernels for whatever reason.
It at least allows them to package it up into an RPM so that it can be
installed just as easy as a regular Mandrake kernel.

b.

-- 
Brian J. Murrell

Attachment: msg76273/pgp00000.pgp
Description: PGP signature

Reply via email to