public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade
Date: Wed, 19 Oct 2005 17:31:04 -0400	[thread overview]
Message-ID: <1129757464.720.15.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1129754698.26382.13.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

On Wed, 2005-10-19 at 21:44 +0100, John Mylchreest wrote:
> I don't particular feel comfortable doing this. the only place I can
> actually see this being of some use is with the pkg_config since an
> ebuild postinst is far too soon, and patching up Kbuild to do this is
> far too intrusive (let alone high maintenance).
> 
> A possibility (although I wouldnt like to promote it through portage)
> would be to have a wrapper/helper script which would do all of this for
> you. build-kernel or some such. But then... whats genkernel for right?

Actually, genkernel does have the --callback option, which runs an
external command before finalizing the build.  We use it for building
external modules and packages that require a configured kernel when
building the releases, but I think adding an option to genkernel
wouldn't be bad to do this for you.  We could add a command-line switch
to genkernel to automatically rebuild any external modules after it has
built the kernel.  We could use something like --autorebuild.  You could
then do something like "genkernel --autorebuild all" to build your new
kernel and automatically rebuild all of your external modules.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-19 21:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 13:32 [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade Herbert G. Fischer
2005-10-19 13:36 ` Henrik Brix Andersen
2005-10-19 14:01   ` Herbert G. Fischer
2005-10-19 17:28   ` John Myers
2005-10-19 18:56     ` Herbert G. Fischer
2005-10-19 18:58       ` Herbert G. Fischer
2005-10-19 20:44         ` John Mylchreest
2005-10-19 21:31           ` Chris Gianelloni [this message]
2005-10-20 17:19             ` John Mylchreest
2005-10-20 19:15               ` Chris Gianelloni
2005-10-20 16:30       ` Jan Kundrát

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=1129757464.720.15.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox