On Fri, 3 Aug 2012 19:58:57 -0400 Greg Freemyer <greg.freemyer@gmail.com> wrote:
All,
I'm trying to get the sub-packages for ssdeep right:
It has a executable of ssdeep, but the shared lib is libfuzzy.so. I currently have a main package of ssdeep and sub-packages of libfuzzy2 and libfuzzy2-devel.
That allows the package to build, but I have no idea if I'm handling the sub-package names correctly. It seems wrong to me and I don't know why the 2 is needed. Is that because the library is libfuzzy v2.7?
This is my %files section of the specfile:
=== %files %defattr(-,root,root) %doc README COPYING %{_bindir}/* %{_mandir}/man1/*
%files -n libfuzzy2 %defattr(-,root,root) %doc README COPYING %{_libdir}/libfuzzy.so.*
%files -n libfuzzy2-devel %defattr(-,root,root) %{_includedir}/fuzzy.h %{_libdir}/libfuzzy.so %exclude %{_libdir}/libfuzzy.a %exclude %{_libdir}/libfuzzy.la ===
Thanks Greg Hi That should be it's soname, you can check on your local build via;
readelf -a /path/to/lib.so | grep -i soname There should be an option to disable-static and you can get rid of the la files via; # Clean up find %{buildroot}%{_libdir} -name '*.la' -type f -delete -print -- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.34-0.7-default up 5 days 21:25, 2 users, load average: 2.06, 2.05, 2.07 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org