From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: The NVIDIA/Kernel fiasco -- is it safe to sync yet?
Date: Sat, 24 Aug 2013 19:45:27 -0500 [thread overview]
Message-ID: <20130824194527.122b5436@fuchsia.remarqs.net> (raw)
In-Reply-To: 52186597.6030407@gmail.com
On Sat, 24 Aug 2013 09:49:43 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 24/08/2013 06:26, Chris Stankevitz wrote:
> > On Fri, Aug 23, 2013 at 9:12 PM, »Q« <boxcars@gmx.net> wrote:
> >> It looks like maybe the best way to tell which ebuilds support
> >> which kernels is to read the conditional for the ewarn message in
> >> each ebuild.
> >
> > If this sort of problem spreads it might be good to build into
> > portage some kind of blocker/keyword mechanism so that users need
> > not deal with this.... not that I have any appreciation for the
> > work involved.
>
> Those tools already exist.
>
> Blockers, which do not really apply here;
In a comment on the bug (which is full of bugspam), someone suggested
blocking kernels which are incompatible with the currently-installed
nvidia-drivers. I'm glad that idea was dismissed.
> elog messages
Those elog messages are presented after compiling a new kernel and then
trying and failing to compile nvidia-drivers. So now I grep the
nvidia-drivers ebuilds for the messages before I compile a new kernel.
A wiki page with info about which nvidia-drivers will build against
which kernels would be a nice thing to have.
next prev parent reply other threads:[~2013-08-25 0:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 17:45 [gentoo-user] The NVIDIA/Kernel fiasco -- is it safe to sync yet? Chris Stankevitz
2013-08-23 18:09 ` Randy Westlund
2013-08-23 22:15 ` Paul Klos
2013-08-24 4:12 ` [gentoo-user] " »Q«
2013-08-24 4:26 ` Chris Stankevitz
2013-08-24 7:49 ` Alan McKinnon
2013-08-25 0:45 ` »Q« [this message]
2013-08-25 16:18 ` Alan McKinnon
2013-08-25 16:34 ` Mick
2013-08-25 20:00 ` hasufell
2013-08-25 20:16 ` Dale
2013-08-25 20:06 ` Alan McKinnon
2013-08-26 1:52 ` »Q«
2013-08-26 6:02 ` Alan McKinnon
2013-08-27 2:06 ` »Q«
2013-08-27 5:57 ` Alan McKinnon
2013-08-27 7:14 ` Pandu Poluan
2013-08-27 7:38 ` Alan McKinnon
2013-08-28 1:41 ` »Q«
2013-08-31 1:40 ` »Q«
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=20130824194527.122b5436@fuchsia.remarqs.net \
--to=boxcars@gmx.net \
--cc=gentoo-user@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