http://bugzilla.rpmfusion.org/show_bug.cgi?id=342
--- Comment #8 from Orcan Ogetbil <oget.fedora(a)gmail.com> 2009-06-23 20:58:08 ---
(In reply to comment #7)
(In reply to comment #6)
> May I ask, what is this for?
> %exclude %{_includedir}/%{name}
> %exclude %{_libdir}
I'm not including devel files. If you think this is a problem, I can, but I
don't know of any application that builds against libtivodecode.a (a static
library).
There are two options:
1) Ask the upstream if they have the API stabilized. If yes, then patch the
Makefile etc to build shared library with proper soname. The tivodecode
executable has to link to this library dynamically. The library file goes to
the libs subpackage and the header files go to the devel subpackage. Then both
the main package and the devel subpackage will require the libs subpackage.
2) If the API is unstable, then put the static library and the header files in
devel subpackage and add "Provides: %{name}-static = %{version}-%{release}" to
the devel subpackage.
> Also, please obey the versioning guidelines for pre-release
packages:
>
>
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#Pre-Release_pack...
Looks like I left out a number. I will fix it to be compliant as
tivodecode-0.2-0.1.pre4.1.
I think it should go like
tivodecode-0.2-0.1.pre4
tivodecode-0.2-0.2.pre4 (minor packaging fix)
tivodecode-0.2-0.3.pre5 (another prerelease)
tivodecode-0.2-1 (final release)
...
--
Configure bugmail:
http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.