/usr/lib64/libsuil-0.so.0 /usr/lib64/libsuil-0.so.0.8.2 /usr/lib64/suil-0/libsuil_gtk2_in_qt4.so /usr/lib64/suil-0/libsuil_qt4_in_gtk2.so /usr/lib64/suil-0/libsuil_x11_in_gtk2.so /usr/lib64/suil-0/libsuil_x11_in_qt4.so
Can i move all these wrap modules into libsuil package itself (libsuil-0-0 that is)? The reason for this is that library is useless without these modules. Consider what happens when there is a libsuil-0.so.1. Then both
On Tuesday 2015-12-08 07:19, Roman Evstifeev wrote: libsuil-0-0 and libsuil-0-1 packages would have the plugins in their filelist => file conflict.
/usr/lib64/libsuil-0.so.1 /usr/lib64/libsuil-0.so.1.0.0 /usr/lib64/suil-0/libsuil_gtk2_in_qt4.so /usr/lib64/suil-0/libsuil_qt4_in_gtk2.so /usr/lib64/suil-0/libsuil_x11_in_gtk2.so /usr/lib64/suil-0/libsuil_x11_in_qt4.so The package is called suil and upstream will most probably call libsuil,
On 08/12/2015 10:50, Jan Engelhardt wrote: libsuil-1 when the major version increments, their api docs go to _docdir/libsuil-0. The libs under suil-0 are plugins so they should go into a plugins package but you have a point Jan. I took this line from wafscript : module_dir = '${LIBDIR}/suil-' + SUIL_MAJOR_VERSION Sorry Roman I've been side tracked by blender out of memory build problems and midnight commander segmentation faults. Regards Dave Plater -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org