From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] rfc: virtual/modutils and module-init-tools
Date: Sat, 25 Feb 2012 00:01:07 -0600 [thread overview]
Message-ID: <20120225060107.GA12218@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
All,
in preparation to unmask udev-181, it was brought to my attention that a
number of packages in the tree have direct dependencies on
module-init-tools. Udev-181 requires kmod, which is a replacement for
module-init-tools.
I have added virtual/modutils to the tree which as of now prefers
module-init-tools over kmod.
The dependencies on module-init-tools in the tree should be changed to
virtual/modutils. I am willing to do this myself if no one objects. If I
do, should I open individual bugs for the packages?
Also, this brings up another question. I replaced module-init-tools in
the system set with virtual/modutils. But, since it is possible to have
a linux system with a monolithic kernel, should this even be in the
system set? If not, once the dependencies are correct, I propose
dropping virtual/modutils from the system set.
On the other hand, if we want virtual/modutils in the system set, there
should be no dependencies in the tree on virtual/modutils.
Thoughts?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-02-25 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 6:01 William Hubbs [this message]
2012-02-25 6:20 ` [gentoo-dev] rfc: virtual/modutils and module-init-tools Mike Gilbert
2012-02-25 7:21 ` Robin H. Johnson
2012-02-25 8:44 ` [gentoo-dev] " Duncan
2012-02-25 17:25 ` William Hubbs
2012-02-25 22:40 ` Duncan
2012-02-25 8:28 ` Duncan
2012-02-25 16:34 ` Mike Gilbert
2012-02-25 20:04 ` Walter Dnes
2012-02-25 22:51 ` Duncan
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=20120225060107.GA12218@linux1 \
--to=williamh@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