Read depends on evince 3.3.2.(And evince 3.3.2 depends on glib 2.31.0<div><br></div><div>Gonzalo<br><div><br><br><div class="gmail_quote">On Tue, Mar 13, 2012 at 7:46 PM, Sascha Silbe <span dir="ltr"><<a href="mailto:silbe@activitycentral.com">silbe@activitycentral.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts from Simon Schampijer's message of 2012-02-10 12:19:02 +0100:<br>
> Sascha, attached is a patch that should update the Fedora deps. I moved<br>
> the 'gnome-python2-evince' dep to the individual Fedora-version configs<br>
> that need it, and created the missing F14-F16 configs.<br>
<br>
Thanks for the patch, but it's not what we need in sugar-jhbuild. Since<br>
we build Read from mainline master, the dependencies need to match what<br>
Read depends on _now_, not at the time of release of the respective<br>
distro.<br>
<br>
I couldn't get it to work on Debian. Can you tell me what the current<br>
dependencies of Read are, in terms of functionality in and versions of<br>
upstream packages, not Fedora package names? Or better yet, can you add<br>
a README that includes that information so that (non-Fedora) packagers<br>
have the same information and can package Read without spending days on<br>
source code analysis and trial-and-error?<br>
<br>
Similar information would be useful for Browse. I did get it to at least<br>
start up (though it shows some SVG icon related Tracebacks in the log<br>
file), but I can't be sure I'm not missing a dependency that's used only<br>
at certain times.<br>
<br>
In an ideal world, I would expect maintainers to announce the above<br>
information on sugar-devel whenever the corresponding change lands in<br>
mainline master.<br>
<span class="HOEnZb"><font color="#888888"><br>
Sascha<br>
<br>
--<br>
<a href="http://sascha.silbe.org/" target="_blank">http://sascha.silbe.org/</a><br>
<a href="http://www.infra-silbe.de/" target="_blank">http://www.infra-silbe.de/</a><br>
</font></span><br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div></div>