https://bugzilla.rpmfusion.org/show_bug.cgi?id=2036
--- Comment #10 from Kevin Kofler <kevin.kofler(a)chello.at> 2011-12-10 05:36:20 CET
---
hmm... I hate to say it, but if this is using the same source as the
package in
Fedora then it should probably be treated like other projects like this. You'll
need to package it just like Fedora but use rpmdiff to generate a rpm diff file
that people can install. I've never done it before so I'm a little short on
details.
Huh? No package in RPM Fusion is packaged as delta/patch RPMs, our toolset
doesn't even support them. What we do is that we package a -freeworld RPM in
RPM Fusion which contains only the files not in the Fedora RPM (by not building
them if possible, or deleting them in %install otherwise), or if that's not
possible, which overrides the files from the Fedora RPM without conflicting
with it.
This chromaprint-tools package is already following the recommended approach.
It's possible that's overkill since you're just adding a
binary, but at a
minimum you'll need to keep to the same version as the Fedora release:
Requires: chromaprint == %{version}
or something like that.
Uhm, no, please only add '='-versioned dependencies on Fedora packages if
absolutely necessary (i.e. if the tools version x are not expected to work with
the library version y≠x)! '='-versioned dependencies mean the packages in
Fedora and RPM Fusion need to be pushed at exactly the same time, which in
practice can only be approximated, so there's always a window where the user
will not be able to update. Thus, please do not gratuitously add them when not
needed.
--
Configure bugmail:
https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.