Hello IOhannes,
I will check it again tomorrow and if I can make a better solution work, I'll implement it.
As for the libmpeg1 vs libmpeg3, how would I specify which one I want to use then? Or does it figure this out on its own at compile time?
-Ilias
IOhannes m zmoelnig wrote:
Ilias Anagnostopoulos wrote:
Hello Roman,
GEM seems to need the specific versions it depends on. I think that since there is no "serious" reason not to use these libraries, it doesn't make sense doing anything to the source code to make it compatible with the newer versions. If we simply provide these extra packages with the PD package, by hosting them on the same places, it will be fine. Since nothing else has anything to do with them, they won't break anything.
i don't think that Gem explicitely needs magick9 rather than magick10. here (debian lenny/sid) i am using imagemagick++10 and everything wors fine.
as for limpeg3 vs libmpeg1: these are not just versions, thes are completely different libraries. replaying the one with the other will certainly make your nose bleed. Gem has source-code support for both libraries. i don't see a reason to remove support for libmpeg1, just because it is no longer packaged. nevertheless, i also don't see any reason why someone should provide a precompiled binary of Gem _with_ support for libmpeg1 (i think it is quite buggy).
so, from my (Gem) side of things: all maintainers of packages should use the latest and greatest available packages of their distribution and not require outdated packages for Gem just because they can :-)
thanks for all your work
gfmadsr IOhannes