--- Comment #9 from Bernard Johnson <bjohnson(a)symetrix.com> 2009-06-24 16:23:23
(In reply to comment #8)
1) Ask the upstream if they have the API stabilized.
Sounds like the API is stable. This is what I received from upstream:
"The API is stable. I wrote an mplayer demuxer prototype that used it (but
I never managed to solve my seeking issues), and also a COM interface
wrapper for Windows (which someone else used to write a .NET application).
One of these days I'll have to release 0.2. The reason I didn't was I
never figured out how exactly I wanted the command line options to save
metadata to work. And I was going to make another program to build a TiVo
file (to allow modifying the metadata and sending the file back to the
TiVo or the TiVo Desktop software)."
So I'll work on shared library route.
Any advice for soname to avoid conflicts with upstream in the future? Just
start with libtivodecode.so.0?
I think it should go like
tivodecode-0.2-0.2.pre4 (minor packaging fix)
tivodecode-0.2-0.3.pre5 (another prerelease)
tivodecode-0.2-1 (final release)
Oops, yes, I'll fix that.
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.