On Fri, 3 Aug 2012 19:58:57 -0400, Greg Freemyer <greg.freemyer@gmail.com> wrote:
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?
The shared library policy, which was created to allow multiple versions of a shared library to be installed in parallel, requires the package to be named <libname><so_major>, i.e. the name of the library with the major version appended. Basically it's the soname (objdump -p will show it) of the library.
%files -n libfuzzy2-devel %defattr(-,root,root) %{_includedir}/fuzzy.h %{_libdir}/libfuzzy.so %exclude %{_libdir}/libfuzzy.a %exclude %{_libdir}/libfuzzy.la
No need to have a versioned devel package when the header is in an unversioned directory. So you can just as well name the package libfuzzy-devel. BTW, if the package uses libtool (as the .la implies) you can either simply pass --disable-static to configure or change the AC_PROG_LIBTOOL in configure.in to LT_INIT([disable-static]) and run autoreconf afterwards. And I'd simply remove the .la file in the install section. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org