<br><br><div class="gmail_quote">On Sun, Apr 10, 2011 at 3:04 AM, Paul Wise <span dir="ltr"><<a href="mailto:pabs@debian.org">pabs@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Apr 10, 2011 at 5:49 PM, Vincent Cheng <<a href="mailto:vincentc1208@gmail.com">vincentc1208@gmail.com</a>> wrote:<br>
<br>
> Oops, don't know why I broke off mid-sentence like that. My point was that<br>
> porting 0 A.D. to work with newer versions of Spidermonkey seems to be a lot<br>
> of work for very little gain and lots of opportunities for potential<br>
> breakage. Philip addressed this already in an earlier message [1].<br>
> However, the Debian Mozilla team doesn't seem to be very enthusiastic about<br>
> supporting an older version of Spidermonkey in the long run. What would be<br>
> the best course of action now? I don't want to pressure upstream to port 0<br>
> A.D. to a newer Spidermonkey version if they have no desire to do so (and I<br>
> have no clue how to port software), I can't pressure the Debian Mozilla team<br>
> to maintain an older Spidermonkey version for a single piece of software<br>
> (and I'm sure that they have a lot of other work to do), and from the<br>
> replies I've seen so far, it seems that embedding Spidermonkey code in 0<br>
> A.D.'s source is a no-no, or at least strongly discouraged.<br>
<br>
</div>Maybe porting to another JavaScript engine (like Google V8) is the<br>
best long-term solution?<br>
<div class="im"><br></div></blockquote><div>Hmmm, I've never thought of porting 0 A.D. to an entirely different JS engine as an option. Is V8's API relatively stable compared to Spidermonkey?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
> In an earlier message [2], you suggested that various .ttf fonts<br>
> (DejaVuSans.ttf, DejaVuSansMono.ttf, texgyrepagella-regular.otf,<br>
> texgyrepagella-bold.otf) should be removed from the source package. But on<br>
> the other hand, since the fonts are source code for the glyphs, they<br>
> shouldn't be removed, right? Sorry, but I can't help but feel somewhat<br>
> confused...<br>
<br>
</div>That was before I knew how they were being used in this package, keep<br>
them in the source package unless upstream introduces build-time or<br>
run-time text rendering.<br>
<div><div></div><div class="h5"><br>
</div></div></blockquote></div><br><div>All right, I'll leave the fonts in the source tarball then.</div><div><br></div><div>- Vincent</div>