El 31/07/14 a las #4, Anton Aylward escribió:
On 07/31/2014 11:55 AM, Cristian Rodríguez wrote:
El 31/07/14 a las #4, Anton Aylward escribió:
WTF! Why? Is this a real dependency that the code has to be there, even if we're not using Wayland, or is this simply "yes another stupid packaging issue"?
It is a real dependency.. code is using the API provided by those libraries.. of course it is not active unless you are running wayland.
Eh?
There's something that doesn't seem right in that explanation.
If Wayland isn't there to make use of the APIs, *and* the APIs are encapsulated in these libraries, then these libraries should be removable if Wayland isn't around to make use of them. Think about the call tree.
That's not how things work..libraries are linked, have a dependency at the binary level, what you are proposing is somehow similar to making the apps use dlopen() to load the libraries on demand.. that ain't gonna work well unfortunately. I 'll let you just the tip of the iceberg.. RPM has no clue how to handle dlopen()'ed libraries, therefore dependency and version handling is let to the packager..and is gonna break everytime the library version changes..plus.. you are requesting this to be done in a component which is under heavy development..its api may or may not be stable..and down the drain we go... -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org