From: John Mylchreest <johnm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade
Date: Wed, 19 Oct 2005 21:44:58 +0100 [thread overview]
Message-ID: <1129754698.26382.13.camel@localhost> (raw)
In-Reply-To: <9f90e8bf0510191158pc96100dl@mail.gmail.com>
> 2005/10/19, Herbert G. Fischer <herbert.fischer@gmail.com>:
> Perhaps the modules-update could be extended to detect new
> kernels and warn users or automatically update modules. This
> could also be documented in Gentoo docs since this is a basic
> and common problem that almost every Gentoo user may have.
module-rebuild shouldn't really have this task. it isn't the right place
to do it. It will of course quite happily do what you need it to do,
rebuild anything which installs a kernel module from portage.
>
> 2005/10/19, John Myers <electronerd@monolith3d.com>
> 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
>
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?
- John
--
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-19 20:54 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 [this message]
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=1129754698.26382.13.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