Mailinglist Archive: opensuse-kernel (77 mails)

< Previous Next >
Re: [opensuse-kernel] kernel-docs package
  • From: Jeff Mahoney <jeffm@xxxxxxxx>
  • Date: Thu, 10 Dec 2009 12:16:04 -0500
  • Message-id: <4B212CD4.4050506@xxxxxxxx>
Hash: SHA1

On 12/10/2009 08:33 AM, Michal Marek wrote:
On 10.12.2009 09:32, Ruediger Oertel wrote:
On Thursday 10 December 2009 01:54:58 Jeff Mahoney wrote:
I propose that we make kernel-docs a linked package to the
kernel-source package and BuildRequires the kernel-source package. The
documentation can be generated with a make -C $SRC O=$PWD instead,
negating the need to copy _anything_. Making it a linked package means
that the version numbers get set automatically by mkspec. Right now, the
kernel-docs package is version 2.6.3 but built against whatever
kernel-source is in the repo.

definitely a good idea. I was part of those that started this package and at
that time I did the copying around of the sources to be able to patch things
whenever "make docs" broke because some source file processor was not
able to grok the source code anymore. If this is more visible to the kernel
hackers (which I assume it will by being in the same source directory)
these issues can be fixed directly instead of hacking around "postmortem" ...

Due to the way the kotd scripts work (no support for dependent builds),
it won't be built as part the kotd. How long does it take to generate
the docs? Maybe we could build it directly from kernel-source.spec. But
let's import it to the kernel git first and then discuss possible

I wonder if there are ways that we can creatively work on dependent
builds. The kernel binaries should be dependent on kernel-source as
well, and mbuild is the only reason they're not. The build service can
handle it. People using rpmbuild can use it. It's mbuild that's the issue.

- -Jeff

- --
Jeff Mahoney
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE -

To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups