bulia byak wrote:
On Mon, 07 Mar 2005 13:42:58 +1100, Peter Moulder <Peter.Moulder@...38...> wrote:
Disadvantages:
- Makes Inkscape source tree about 1MB bigger, and increases Inkscape's memory usage at runtime.
Why is memory usage increased, compared to loading a lib?
- Any bug fixes to libcroco would have to wait until at least one release of Inkscape before being fixed. This is most of concern if the bug fix is security-related.
This means that the answer to your question (whether to include libcroco) depends on how frequent are the upstream libcroco updates. If it has stalled or is slow, we should better include it here. Otherwise, we should link. Including is easier for our users (less dependencies), and it has worked well for potrace (which hasn't stalled, but its updates are infrequent and, in part, driven by Inkscape activity). From what I know about libcroco, including it seems to be a better option.
Speaking of which, I hope that nobody was affected by the quick update from Potrace1.6 ---> to --->1.7 that I performed during the weekend. It was a bugfix release from Peter.
Bob