On Fri, 2015-02-13 at 14:36 +0100, drago01 wrote:
> On Mon, Nov 17, 2014 at 8:06 PM, Adam Jackson wrote:
> > Since the modular X repackaging in FC5, we have limited X server updates
> > such that the ABI does not change. F20 shipped with xserver 1.14.4, for
> > example, so we might update it to 1
On Mon, Nov 17, 2014 at 8:06 PM, Adam Jackson wrote:
> Since the modular X repackaging in FC5, we have limited X server updates
> such that the ABI does not change. F20 shipped with xserver 1.14.4, for
> example, so we might update it to 1.14.7 but not to 1.15.0. With the
> reduced driver set in
On Tue, Nov 18, 2014 at 2:24 AM, Thorsten Leemhuis wrote:
> Lo!
>
> Adam Jackson wrote on 17.11.2014 20:06:
>>
>> With that in mind, I ask for feedback on how we'd actually like that to
>> work. The kernel rebase policy seems like a pretty reasonable model:
>> F21 would stay on 1.16.x until there
On Tue, 2014-11-18 at 08:24 +0100, Thorsten Leemhuis wrote:
> But in the end Fedora and its kernel maintainers didn't care. Which
> might be the right thing to do for X as well, because companies then
> learn that they need to keep track of ongoing development and users
> notice some of the risks
Lo!
Adam Jackson wrote on 17.11.2014 20:06:
>
> With that in mind, I ask for feedback on how we'd actually like that to
> work. The kernel rebase policy seems like a pretty reasonable model:
> F21 would stay on 1.16.x until there's an upstream 1.17.1 release, and
> (if F20 were to be affected by
On 11/17/2014 04:16 PM, Rahul Sundaram wrote:
1) proprietary drivers depend on the kernel
Aren't there two parts, the kernel driver and the X driver? From the
earlier discussion, it sounds like some part depends on the X server ABI.
2) yes people do build from source but indirectly via th
On Mon, Nov 17, 2014 at 4:50 PM, Samuel Sieb wrote:
My opinion is strongly in line with Kevin, but Chris has a good point.
> However, isn't it possible to have both. I'm not familiar with the
> proprietary drivers other than knowing that the NVidia one is available
> through rpmfusion. (Out of t
On 11/17/2014 12:54 PM, Chris Adams wrote:
Once upon a time, Kevin Kofler said:
IMHO, we should not let proprietary drivers hold us hostage that way. We do
not and should not support them. We don't even ship them. So we should just
upgrade X if the software we ship is ready for it. If some prop
Once upon a time, Kevin Kofler said:
> IMHO, we should not let proprietary drivers hold us hostage that way. We do
> not and should not support them. We don't even ship them. So we should just
> upgrade X if the software we ship is ready for it. If some proprietary
> driver breaks, its users ge
Adam Jackson wrote:
> One thing we might have to play by ear is the interaction with binary
> drivers. The nvidia legacy driver, for instance, does not always have
> builds available for arbitrarily new servers, which means updating the X
> server might change you to an nvidia driver that no longe
On 17 November 2014 20:06, Adam Jackson wrote:
> Since the modular X repackaging in FC5, we have limited X server updates
> such that the ABI does not change. F20 shipped with xserver 1.14.4, for
> example, so we might update it to 1.14.7 but not to 1.15.0. With the
> reduced driver set in F21
Since the modular X repackaging in FC5, we have limited X server updates
such that the ABI does not change. F20 shipped with xserver 1.14.4, for
example, so we might update it to 1.14.7 but not to 1.15.0. With the
reduced driver set in F21 it's now much more reasonable to push updates
to older re
12 matches
Mail list logo
