> Fedora doesn't apply are rolling release model.
> It applies an API/ABI-stable within one release model.
> In general, this means, packages can only be upgraded
> if they do not break these packages' API/ABI.
Because Mesa has already been updated twice after the F20 release (9.2 -> 10.0 -> 10.1), I don't suppose updating to 10.2 or should cause a lot of issues.
Furthermore, as the only external mesa interface is OpenGL which is required to be stable anyway, there is no big risk involved.
All the internal interfaces (xorg, drm, ...) can be taken care by the distribution.
> If you are very eager for the latest — and it sounds like you are! — I
> encourage you to try the alpha release, or even run Rawhide, as I do.
I did that, but rawhide is built with debug compiler options and therefore notably slower (at least phoronix benchmarks say so) - and it usually breaks quite regulary.
> Or, if Mesa is your primary concern, you might also contact Felix Schwarz
> about making a Mesa 10.3 Copr, as he did with 10.1 previously before that
> hit the distribution — take a look at
> <https://copr.fedoraproject.org/coprs/fschwarz/mesa10/>.
I used that 10.1 repository before 10.1 was pushed to F20, it would be great if it would exist for 10.3 too.
I'll ask Felix, hopefully I'll be able to motivate him ;)
- Gerhard
> encourage you to try the alpha release, or even run Rawhide, as I do.
> Or, if Mesa is your primary concern, you might also contact Felix Schwarz
> about making a Mesa 10.3 Copr, as he did with 10.1 previously before that
> hit the distribution — take a look at
> <https://copr.fedoraproject.org/coprs/fschwarz/mesa10/>.
I used that 10.1 repository before 10.1 was pushed to F20, it would be great if it would exist for 10.3 too.
I'll ask Felix, hopefully I'll be able to motivate him ;)
- Gerhard