On Saturday, June 15, 2013 12:04:18 AM Ma Xiaojun wrote:
> On Fri, Jun 14, 2013 at 11:55 PM, Scott Kitterman <email@example.com>
> > As I mentioned, I'm relying on what upstream kwin has said. I know there
> > have been times (quantal) when Ubuntu moving to a new mesa version in a
> > manner that, from the perspective of our upstream, was overly aggressive
> > caused problems. I would assume that was done because the features were
> > wanted for Ubuntu specific reasons and not just version chasing. It may
> > be no more than that.
> http://packages.qa.debian.org/m/mesa.html looks quite messy :)
> And I checked building flags, Arch Linux enables more stuff.
Arch also think /usr/bin/python --> /usr/bin/python3 is a reasonable thing to
> And I noted that we may need separate the build of libOSMesa and rest
> of Mesa. As libOSMesa built with --enable-shared-glapi is considered
> And still want to see where are the bugs remotely caused by Unity?
That isn't what I said.
Kubuntu has always relied on the infrastructure provided in the Ubuntu archive
to build our KDE variant on top of. It's pretty obvious to me that, at some
point, this will no longer be feasible. The Kubuntu team certainly doesn't
have the manpower or expertise to maintain their own X/Wayland stack.
If, in the long run, the answer is to rely on Debian's maintenance effort for
that, then the value of being part of the Ubuntu project is substantially
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel