*** This bug is a duplicate of bug 1192908 ***
https://bugs.launchpad.net/bugs/1192908
This bug is still valid. We don't have a problem at this point, because
we have both mir and mesa packages in the archive, so we can build new
versions using the existing versions of -dev packages to fulfill
dependencies (this needs some care when we make incompatible changes).
I agree that our best way forward is to remove the dependency libegl1
-mesa-dev has on libmirclient-dev. It's reasonable to assume that a
program that needs to use Mir with EGL will depend on libmirclient-dev
itself, or at least mircommon-dev (otherwise how can it know about the
MirConnection/Surfaces types it needs to pass to EGL?).
I would also recommend changing mesa to build-depend on mircommon-dev
instead of the full libmirclient-dev, since it only needs the Mir EGL
definitions in the former package.
Note, though, that as Daniel points in bug #1192908, we have a circular
dependency issue at the source package level, that can't be solved
unless we either use multiple source packages for Mir, or move our Mir
Mesa EGL definitions upstream in Mesa, as Kevin suggested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239037
Title:
circular build-dependency between mesa, mir
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1239037/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
