ext Jannis Pohlmann <[email protected]> writes: > * some modifications (thinking PNG->JPEG here for example) in > maemo-af/tumbler are incompatible and will not be accepted into > upstream without the approval of other, related open source projects
We can try to make it so that tumbler is configurable enough (compile-time and run-time). The default configuration would be spec compliant, and Maemo / MeeGo / Harmattan can cleanly configure it for their needs without having to deviate from the upstream source. E.g., you could have support for both JPEG and PNG in your tree, but JPEG would not normally be enabled. Out-of-tree plugins are an option, too. > * I can bump the upstream version to something higher than whatever > version Maemo/MeeGo have now if that helps; I'd prefer that version > to be 0.1.x though, as per Xfce convention 0.2.x would refer to a > stable branch and I'm not sure we're quite there yet Yes, good point. What about 0.1.20? It might be difficult and/or slow for me to find anyone who could officially work on this right now on the Nokia side. That's why I also think that reverting tumbler in MeeGo to the upstream version is best right now. Jannis, if you can tag 0.1.20 quickly, someone could just upload it to MeeGo. That should be slightly cleaner than reverting to 0.1.6, I think. Alexander Bokovoy has already initiated a discussion about changes to the thumbnailing spec that would allow us to use the important performance improvements while still being compliant. Thanks a lot Alexander! Unfortunately, if we would have to decide between being thumbnailing spec compliant in MeeGo Handset, or getting the performance we need, we will have to sacrifice compliancy. This has hopefully only a small impact, since most applications should be isolated from this via abstractions like libthumbnail. _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
