From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: evdev broken?
Date: Thu, 21 Jul 2011 12:13:09 -0400 [thread overview]
Message-ID: <4E285015.5060406@orlitzky.com> (raw)
In-Reply-To: <20110721095712.755efe5a@zaphod.digimed.co.uk>
On 07/21/2011 04:57 AM, Neil Bothwick wrote:
> On Wed, 20 Jul 2011 18:34:03 -0400, Michael Orlitzky wrote:
>
>>>> I've always wondered why, if portage knows that has to be done, can't
>>>> portage just go ahead and do it?
>>>
>>> Now that we have a set to do this, I see no reason why this could not
>>> be an option, enabled by a USE flag.
>>>
>>>
>>
>> The last time I complained about this, someone sent me here:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=192319
>
> That seems to be discussing ABI changes. The X drivers situation is
> different. Also, that issue has largely been resolved, in as much as ABI
> changes don't break things like they used to, with @preserved-rebuild.
>
>
Huh? If implemented, that would allow
FORCEREBUILD=x11-drivers/xf86-input* on major Xorg upgrades.
next prev parent reply other threads:[~2011-07-21 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 2:50 [gentoo-user] evdev broken? Francisco Ares
2011-07-20 3:05 ` [gentoo-user] " Grant Edwards
2011-07-20 3:10 ` Francisco Ares
2011-07-20 3:38 ` Francisco Ares
2011-07-20 6:05 ` Mick
2011-07-20 6:20 ` Dale
2011-07-20 11:27 ` Francisco Ares
2011-07-20 12:03 ` Alex Schuster
2011-07-20 11:23 ` Francisco Ares
2011-07-20 14:16 ` Grant Edwards
2011-07-20 14:36 ` Mick
2011-07-20 16:36 ` Alan McKinnon
2011-07-20 19:01 ` Grant Edwards
2011-07-20 16:37 ` Neil Bothwick
2011-07-20 22:34 ` Michael Orlitzky
2011-07-21 8:57 ` Neil Bothwick
2011-07-21 16:13 ` Michael Orlitzky [this message]
2011-07-21 16:44 ` Neil Bothwick
2011-07-20 3:05 ` [gentoo-user] " Arthur Barlow
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=4E285015.5060406@orlitzky.com \
--to=michael@orlitzky.com \
--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