--- Comment #16 from NicolasChauvet <kwizart(a)gmail.com> 2008-11-27 18:22:35 ---
Created an attachment (id=37)
rpmsodiff between fedora/rpmfusion 1.0-2
this log show the diff between symbols available in the fedora elf library and
the rpmfusion one. The rpmfusion one has symbols added, which is what we could
expect with the ffmpeg-devel addition as BR (along with the expat-devel fix
that seems to be enought to link to the system shared expat and added the XML
Now that seems a little more scary about symbols that are removed; since a
third part library/binary might rely on these symbols from the fedora package
and hence, that's what we call Application Binary Interface to collapse,( aka
The question is then:
Are theses symbols exposed to the API or only used internaly from the wxsvg
library. At this time I'm not sure about how to check (there is a need to check
the wxsvg-devel header at least). But still the symbols removal is suspect.
(why adding BR will remove symbols?). And maybe some code is conditionalized.
for now that would be fine to have the expat-devel added to the fedora package
and the expat sources removed between configure and make (so we are sure not to
use the internals headers at fedora wxsvg built time).
Then we will compare the two built more easily.
If we cannot assure ABI from the fedora to the rpmfusion package to be
preserved, then we might work on another solution with a library soname change
(rename).but fedora packages that will use fedora wxsvg won't be able to use
That makes me wonder which package "can" use wxsvg and if a ffmpeg-less version
of wxsvg is "at the end" usable.
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.