Quoting Stefan Seyfried
Am 27.03.2013 16:00, schrieb darx@sent.com:
The upstream 5.1 vs 5.2 politics are not something I can solve.
namespace-separated headers is already done in-distro. e.g. /usr/include/gtk-{2.0,3.0}, /usr/include/python-{2.7,3.0}, etc.
This is done by gtk-upstream.
why is /usr/include/lua-{5.1,5.2} such a problem?
you would need to patch every single program you would want to compile (or add custom CFLAGS and stuff).
that's the job of pkg-config and as such the provided .pc file.. BUT: as upstream has only one namespace (lua), anybody will be using pkg-config --cflags lua to find the right location of the headers... we can not change the name of the .pc file without breaking everything. so, yes.. moving the /usr/include stuff out into /usr/include/lua-5.[12] is possible, but does not solve everything... just check what lua(-51)?-devel provides on file level: /usr/include/lauxlib.h /usr/include/lua.h /usr/include/lua.hpp /usr/include/luaconf.h /usr/include/lualib.h /usr/lib64/liblua.a /usr/lib64/liblua.so /usr/lib64/pkgconfig/lua.pc => /usr/include => solvable => /usr/lib64/liblua.a (eeks.. that should live in a -devel-static anyway!) => /usr/lib64/liblua.so => tough.. => /usr/lib64/pkgconfig/lua.pc => no way to change the name without breaking everything. so before looking at the whole picture, solving the small issue being the location of the headers is 100% waste of time. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org