From: Carlos Silva <r3pek@r3pek.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-drivers/nvidia-drivers: nvidia-drivers-313.18.ebuild ChangeLog
Date: Sun, 3 Mar 2013 14:49:38 -0100 [thread overview]
Message-ID: <CA+ZvHYFW6zF9AFDLFZVZeUSGKi4L121dEesmJzuLcVZsJDgLtw@mail.gmail.com> (raw)
In-Reply-To: <51336170.1030802@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Sun, Mar 3, 2013 at 1:42 PM, hasufell <hasufell@gentoo.org> wrote:
> What do we have useflags for in gentoo?
>
> add a "unsupported-kernels" useflag, mask it, add a clear statement in
> the masking reason and be done
>
Not a bad solution, still, I, as a user, don't think making the compilation
work with a specific kernel should be considered "unsupported". How many
times modules stop working because the kernel changed something that
breakes compilation? And I'm not only talking about closed source drivers,
even open source ones have this "problem", but in fact, they are fixed
faster.
Does the gentoo community really need this kind of strictness? Don't think
so.
[-- Attachment #2: Type: text/html, Size: 1157 bytes --]
next prev parent reply other threads:[~2013-03-03 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130302160257.B3FCB2171D@flycatcher.gentoo.org>
2013-03-03 7:01 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-drivers/nvidia-drivers: nvidia-drivers-313.18.ebuild ChangeLog Samuli Suominen
2013-03-03 7:11 ` Alec Warner
2013-03-03 7:40 ` Samuli Suominen
2013-03-03 8:34 ` Tom Wijsman
2013-03-03 14:42 ` hasufell
2013-03-03 15:49 ` Carlos Silva [this message]
2013-03-03 16:27 ` Alec Warner
2013-03-03 17:24 ` Ryan Hill
2013-03-03 20:56 ` Chí-Thanh Christopher Nguyễn
2013-03-03 22:05 ` hasufell
2013-03-03 23:09 ` Ryan Hill
2013-03-04 3:44 ` Rick "Zero_Chaos" Farina
2013-03-04 18:28 ` Samuli Suominen
2013-03-05 3:26 ` Ryan Hill
2013-03-04 18:25 ` Samuli Suominen
2013-03-03 17:39 ` Ryan Hill
2013-03-03 18:11 ` Carlos Silva
2013-03-03 23:11 ` Nikos Chantziaras
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=CA+ZvHYFW6zF9AFDLFZVZeUSGKi4L121dEesmJzuLcVZsJDgLtw@mail.gmail.com \
--to=r3pek@r3pek.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