Stephan Kulow wrote:
The longest path worries me a lot though, but I have no good idea how to avoid e.g. swig being behind mysql.
Maybe swig could be eliminated in that path. Looks like lcms needs it for it's python bindings only. By building the python bindings in a separate spec file lcms itself wouldn't depend on swig anymore. I also wonder why graphviz depends on ksh and bind on mysql. Maybe bind could be modified to build the database drivers separately. Alternatively a minimal bind package with reduced dependencies could be created that is used for building only. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org