On Fri, 23 Aug 2013 23:12:39 -0500
»Q« <[email protected]> wrote:
> On Sat, 24 Aug 2013 00:15:40 +0200
> Paul Klos <[email protected]> wrote:
>
> > Op vrijdag 23 augustus 2013 14:09:59 schreef Randy Westlund:
> > > On Fri, Aug 23, 2013 at 10:45:46AM -0700, Chris Stankevitz
> > > wrote:
> > > > Are "regular" nvidia users who run a completely stable system
> > > > (with only stable nvidia-drivers and stable gentoo-sources)
> > > > affected by any of this?
> > >
> > > I believe so. I run testing, but this just cleared up for me a
> > > few days ago when I went to kernel 3.10.7 (stable). I'm currently
> > > running kernel 3.10.9 and nvidia-drivers 325.15 (both testing),
> > > which works just fine. Try it and see what happens.
> >
> > Updated to gentoo-sources 3.10.7 (stable) today. I had (stable)
> > x11-drivers/nvidia-drivers-319.32 which failed rebuilding. After
> > keywording x11-drivers/nvidia-drivers I'm on 325.15 as well. Seems
> > to be fine so far.
>
> Same here, amd64
>
> 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.
This script works with the nvidia-drivers ebuilds currently in the
tree. If the format of the ewarn messages changes, it won't.
#!/bin/sh
# This quick-and-dirty script checks the available nvidia-drivers
# ebuilds to show you which are meant to build against which kernel
# versions.
# If you use grep without pcre support, you get to rewrite the grep line.
[ -f /etc/make.conf ] && . /etc/make.conf
[ -f /etc/portage/make.conf ] && . /etc/portage/make.conf
echo
for ebuildversion in $(ls "${PORTDIR}"/x11-drivers/nvidia-drivers/*.ebuild)
do
echo ${ebuildversion##*/} supports
grep -Po '<sys-kernel.*\d' "${ebuildversion}"
echo
done
exit
