From: John Mylchreest <johnm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade
Date: Thu, 20 Oct 2005 18:19:32 +0100 [thread overview]
Message-ID: <1129828772.9643.2.camel@localhost> (raw)
In-Reply-To: <1129757464.720.15.camel@cgianelloni.nuvox.net>
On Wed, 2005-10-19 at 17:31 -0400, Chris Gianelloni wrote:
> 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.
My thoughts exactly. And I'm sure a welcome addition.
--
Role: Gentoo Linux Kernel Lead
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 9C745515
Key fingerprint: A0AF F3C8 D699 A05A EC5C 24F7 95AA 241D 9C74 5515
Web:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9C745515
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-20 17:28 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
2005-10-20 17:19 ` John Mylchreest [this message]
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=1129828772.9643.2.camel@localhost \
--to=johnm@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