El sáb, 18-10-2014 a las 12:15 -0700, Josh Andler escribió:
On Sat, Oct 18, 2014 at 6:22 AM, Gez <listas@...3059...> wrote:
As the user who reported the bug being discussed, I'd like to add that for my workflow (and I'm sure that many people's workflows too) including bitmap images in vector illustrations is a critical feature. Removing the ability to work with bitmaps is a no-go. If I install Inkscape from the repositories and find that I would immediatelly roll back to the previous version. People getting a program from repository expects that the program works. Period.
Anyone who would be getting it from a repository (minus the Stable PPA unless we provide cairo there too) WILL HAVE the correct version of cairo. It has been released. When it comes to spring distro releases, it will not be an issue. It will really only potentially be an issue for LTS users who want to compile Inkscape themselves. You keep saying from repos, so I need to emphasize, it won't be an issue for people getting it from vendor repos.
You say it's not an issue because at the time of the release of Inkscape all the distros that could offer inkscape 0.91 will already have the right version of Cairo, right? That's true, and I know this is rather unlikely, but if some distro decides to stick to the previous version of Cairo for whatever reason and a packager builds inkscape for their repos, the issue would affect all of their users.
It's unlikely but not impossible.
LTS users who want to compile themselves, on the other hand, are better equiped to deal with a dependency not met. As I mentioned earlier, you can install the right cairo version in a different prefix and load it when the inkscape binary is executed (that's how I tried it without messing with my system-wide cairo).
My point is that people who chose an LTS distro but want to run a new version of the program that they can only get by compiling the sources, are probably prepared to deal with it, and building the new cairo will be at their reach. Using Inkscape with the old cairo brings back a very nasty bug that breaks lots of people's workflows. Making the new version of a dependency avoids that and only creates an extra problem to people who are likely to be able to deal with it.
G.