[scribus-dev] Scribus Dependency Tracking
John L. Poole
jlpoole56 at gmail.com
Sat Mar 12 14:40:30 UTC 2016
I encountered a bug in the poppler library (0.39.0) supporting the
On Jean Ghali's advice, I participated in a bug with the poppler team at
I provided a patch against the 0.39.0 version.
A poppler developer reponded asking me to basically test against
their current version which is
at 0.41.0. That brings me to ask this question:
Is there a matrix or something to track Scribus' dependencies?
For example, the version of poppler offered for the windows build
of Scribus is at version 0.39.0. Is there reason why 0.39.0 could
not be replaced with 0.41.0? There ought to be some place where
a developer can visit to see what versions of a dependency work, or
more importantly, do not work and for what reason.
I checked my Gentoo Linux environment where I build Scribus and see
that I have poppler 0.32.0!
Would having pages of tables on the Scribus wiki that track each
dependency indicating what works, and what cannot work (because of
recent code changes) be useful?
It would be a waste of my time to try poppler 0.41.0 on Windows when
it is known by others that version 0.41.0 will not work because of
reason yadda..yadda. There needs to be some sort of collaborative
point where knowledge of a dependency is tracked.
More information about the scribus-dev