Dana 9.2.2013 17:35, Andreas Radke je napisao:
Now that Wayland has landed in Community I can build Mesa with support for Wayland. This leads to a new dependency in libegl: libegl E: Dependency wayland detected and not included (libraries ['usr/lib/libwayland-server.so.0', 'usr/lib/libwayland-client.so.0'] needed in files ['usr/lib/egl/egl_gallium.so','usr/lib/libEGL.so.1.0.0']) Since cairo will also depend on that libegl then every system will pull in Wayland. Is this really needed? If we can't build it in a different way we directly need to move Wayland to extra. -Andy
libEGL.so is linked to libwayland libraries so there is really no way to split it unless you produce libegl-wayland package that includes libEGL and libwayland-egl and make default libegl package ship libEGL without Wayland deps (would be needed to be rebuilt twice).
I've already filled a bug for libgbm package ... It doesn't install pipe_* and egl_gallium.so in /usr/lib/libgbm (althrough maybe egl_gallium.so should be installed in libegl package)
https://bugs.archlinux.org/task/33780
