[Bug 49] wxsvg-freeworld - C++ library to create, manipulate and render SVG files
http://bugzilla.rpmfusion.org/show_bug.cgi?id=49
--- Comment #13 from Stewart Adam <s.adam(a)diffingo.com> 2008-11-14 06:04:44 ---
(In reply to comment #11)
You can't do that. Even if it contains just a single .so symlink,
devel
symlinks MUST be in a -devel package, no exceptions
We'll have to ignore
rpmlint's error about no binary files in usr/lib then.
Besides being more practical, I figured error > warning so it was better to put
it into the main package ;)
Here it is with a split -devel:
SPEC: http://downloads.diffingo.com/rpmfusion/wxsvg-freeworld.spec
SRPM:
http://downloads.diffingo.com/rpmfusion/wxsvg-freeworld-1.0-2.fc10.src.rpm
(In reply to comment #12)
Also:
* How does one build against the .so symlink in the private directory? Manual
-L flag hackery?
Yup, AFAIK there's no other way. It's not great, but
it's better than
conflicting with the Fedora installation of wxsvg (in which case nothing would
work at all). We have the same situation for the nvidia libs vs mesa libs for
example.
* Are you SURE there's binary compatibility in the sense that
packages linked
against the Fedora wxsvg will work with this one? (I'm asking because the
necessity to link against the .so from wxsvg-freeworld is indicative of some
binary incompatibility, but it can still be compatible in the direction which
is actually relevant.) Please test some packages using wxsvg in Fedora with
wxsvg-freeworld installed to make sure they still work with the replaced
library. If they don't, you'll have to rename the library (to something like
libwxsvg.so.0fw), not move it and have it override the Fedora version.
Other than
the addition of some (ffmpeg-related) functions, everything should
be identical. I've tested using svgview from the Fedora package while the
overrides are active and everything still functions as expected.
--
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.