[manjaro-dev] [Xorg] X.org X-Server 1.15 around the corner and what it means

[Rob]

The thing is, it's not really a "Linux wide" issue, the only people
affected are the leading/bleeding edge rolling releases, of which there
aren't many and big companies like AMD and nVidia care less about.

Also, IMO any type "it'll also affect Arch" argument in regard to catalyst
driver is moot, because Arch does not officially support catalyst (it got
pulled from their main repos and kicked to AUR years ago), but it is
officially supported in Manjaro .

I don't deny my opinion is probably quite biased though, considering my
belief is that bleeding edge software and the rolling release system is a
bad choice for novice Linux users.


On Wed, Nov 6, 2013 at 4:33 AM, J Fernyhough <j.fernyhough at gmail.com> wrote:

> I personally don't see a problem with a solution similar to Catalyst
> Legacy. If there is a Linux-wide issue with AMD proprietary drivers
> and Xorg 1.15 then Manjaro won't be the only ones affected (i.e. so
> will Arch). Given the leaps made by the OSS radeon driver under Linux
> 3.11 I'd personally be reticent to hold back other packages because of
> one proprietary driver. For example, would you be holding back Linux
> 3.12 because ZFS/SPL hasn't yet been updated with 3.12 support? Once
> kernel 3.11 becomes default, I reckon the default position should be
> to "try free first" (and in many cases people only want Catalyst
> because they're used to needing it).
>
> J
>
> On 5 November 2013 09:34, Rob <korrode at gmail.com> wrote:
> > Depends on if you want to always arbitrarily roll Arch updates in or
> not. If
> > i was you I would have no problem holding back the Xorg server for ages
> > after Arch has upgraded it, waiting for AMD to release new drivers. Who
> is
> > going to feel a negative effect from a slightly older X11? Certainly not
> the
> > average Manjaro user... unless there's something i'm not considering?
> >
> >
> >
> > On Tue, Nov 5, 2013 at 5:27 PM, Philip Müller <philm at manjaro.org> wrote:
> >>
> >> Some might not know it yet but Xorg X-Server 1.15 RC1 got tagged. This
> >> means again a ABI bump which will break Catalyst and Nvidia. I see no
> issues
> >> for Nvidia to release a working proprietary blob but I see red for AMD
> once
> >> more. Sure, I already found a solution to ship catalyst-server,
> >> catalyst-video and catalyst-input which is simply an outdated
> xorg-stack you
> >> have to install to get this bollugs working.
> >>
> >> This means again to ship those extra packages we only need for Catalyst
> >> and for x86_64 never reach a CD-size if that matter. Also it means
> you'll
> >> never get the new features X-Server 1.15 series might offer.
> >>
> >> I don't know if SteamOS will change anything on this topic. The fact is,
> >> Arch will ship this new xorg-stack series soon or later.
> >> Which leaves me to two options:
> >>
> >> Keep Xorg-Stack 1.14 and maintain it on our terms
> >> Keep up with Arch and use our catalyst-stack solution
> >> Or ditch Catalyst once for all and don't give a #$%&§ about it
> >>
> >>
> >> Thoughts, whishes
> >>
> >> Phil
> >>
> >> _______________________________________________
> >> manjaro-dev mailing list
> >> manjaro-dev at manjaro.org
> >> http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
> >>
> >
> >
> > _______________________________________________
> > manjaro-dev mailing list
> > manjaro-dev at manjaro.org
> > http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
> >
> _______________________________________________
> manjaro-dev mailing list
> manjaro-dev at manjaro.org
> http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.manjaro.org/pipermail/manjaro-dev/attachments/20131106/bf719cf0/attachment.html>