Krzysztof Kosiński wrote:
Joshua L. Blocher wrote:
Yes, it is. 2geom is in fact a separate library that we carry in tree for easy of updating (...)
That's contradictory for me. If updating the library in the Inkscape tree is allowed then the warning is not intact, because it says not to update files. I know that lib2geom is a separate library, but are the changes from Inkscape tree merged back into the lib2geom tree, or are they discarded whenever an upstream change happens?
Regards, Krzysztof Kosiński
Krzysztof,
Joshua (the other one) pointed out that there are no distros that anyone is aware of carrying lib2geom yet, so it is a necessity for us to carry it in-tree currently. If changes need to be made in 2geom, they need to get made upstream and then the modified file(s) pulled into Inkscape SVN.
The comment about ease of updating is because things in 2geom have changed quite a bit since the transition to it within Inkscape had begun. Not having it in-tree (with the library being so young) then forces another dependency on our nightly/svn users and testers (for all platforms), which given the transition and testing at hand, will cause bug reporting and testing issues because the rev of 2geom would get out of sync on different users systems.
It won't always be the case for it to be in-tree... but that's just the way it is for the time being.
Cheers, Josh