From: John Myers <electronerd@monolith3d.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade
Date: Wed, 19 Oct 2005 10:28:38 -0700 [thread overview]
Message-ID: <200510191028.43618.electronerd@monolith3d.com> (raw)
In-Reply-To: <20051019133630.GA30454@dmz.brixandersen.dk>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Wednesday 19 October 2005 06:36, Henrik Brix Andersen wrote:
> On Wed, Oct 19, 2005 at 11:32:19AM -0200, Herbert G. Fischer wrote:
[snip]
> > - Patch kernel's "make" to warn at the end of "make modules_install"
[snip]
> I think you should check out sys-kernel/module-rebuild
Actually, a combination of these might not be a bad idea.
Something like this (not tested):
if [ -n "$(which module-rebuild 2>/dev/null)" ] ; then
if [ -n "${AUTO_MODULE_REBUILD}" ] ; then
echo "Rebuilding external modules:"
module-rebuild ${MODULE_REBUILD_OPTIONS} rebuild
else
echo "You might want to rebuild the following external modules:"
module-rebuild -XC list | tail -n +2
echo
echo "You can use module-rebuild to do that."
echo "If you want to have your external modules automatically rebuilt"
echo "when making a kernel's modules_install target, set"
echo "AUTO_MODULE_REBUILD in your environment. You can set"
echo "MODULE_REBUILD_OPTIONS to options to pass to module-rebuild."
echo "(-X for example)"
fi
else
echo "You might want to emerge sys-kernel/module-rebuild to keep track of"
echo "kernel modules you've installed with emerge"
fi
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-10-19 17:29 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 [this message]
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
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=200510191028.43618.electronerd@monolith3d.com \
--to=electronerd@monolith3d.com \
--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