<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-11 16:20 GMT+02:00 David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5">On Sun, May 11, 2014 at 09:38:06AM +0200, Nicolas Cellier wrote:<br>
> 2014-05-11 9:18 GMT+02:00 Nicolas Cellier <<br>
> <a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>>:<br>
><br>
> ><br>
> > 2014-05-11 3:48 GMT+02:00 David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>>:<br>
> ><br>
> > On Sat, May 10, 2014 at 03:00:41PM -0700, tim Rowledge wrote:<br>
> >> > There?s a related issue that could do with a fix sometime - the jpeg<br>
> >> library we used to make the jepegreadwriteplugin is out of date and Debian<br>
> >> (at least) considers that a security risk and thus they mangle the sources<br>
> >> to not use those file but link to the ?standard? library. Which<br>
> >> unfortunately doesn?t actually work within our plugin!<br>
> >> ><br>
> >> > Leaving aside the sheer rudeness of throwing unapproved ?patches? into<br>
> >> somebody?s code (without ever letting Ian know, for example) and resulting<br>
> >> in a broken function, I imagine that if looked into we would be able to<br>
> >> tweak our plugin code to actually work with the new jpeg library code. This<br>
> >> would be a Good Thing. If anyone knows enough about jpeg library, Debian,<br>
> >> blah blah blah to look into this then it might make a nice project that<br>
> >> would benefit the Raspberry Pi Scratch using world - several tens of<br>
> >> thousands of kids in the UK alone.<br>
> >> ><br>
> >><br>
> >> This issue is tracked in Mantis 7539: "Plugins should use platform<br>
> >> libraries<br>
> >> where possible. Gentoo removed Squeak for this reason."<br>
> >><br>
> >> <a href="http://bugs.squeak.org/view.php?id=7539" target="_blank">http://bugs.squeak.org/view.php?id=7539</a><br>
> >><br>
> >> It was originally reported based on Gentoo rejecting Squeak, and it<br>
> >> affects Debian<br>
> >> and other Linux distributions that (quite reasonably) expect that<br>
> >> supported<br>
> >> applications should link to current versions of system libraries.<br>
> >><br>
> >> If anyone is interested in working to improve this, please do. It would<br>
> >> be a great<br>
> >> way for someone to contribute a really useful update to the VM.<br>
> >><br>
> >> Dave<br>
> >><br>
> >><br>
> >><br>
> > A general idea would be to proceed in two steps:<br>
> > -1) upgrade the library in squeak svn repository, so as to fix the API<br>
> > evolutions mismatch<br>
> > -2) provide a way to link to existing library (via cmake/configure in<br>
> > VMMaker and apt/rpm package dependency at distrib level)<br>
> ><br>
> > Good plan, but what are the starting points?<br>
> > Which library exactly should be used?<br>
> > libjpeg - <a href="http://sourceforge.net/projects/libjpeg/" target="_blank">http://sourceforge.net/projects/libjpeg/</a> - which is the<br>
> > successor of the library used in squeak is licenced GPL v2, should we taint<br>
> > the whole VM?<br>
> > There is also an opened issue (<a href="http://sourceforge.net/p/libjpeg/bugs/5/" target="_blank">http://sourceforge.net/p/libjpeg/bugs/5/</a> -<br>
> > 5 years old!!!) telling it does not compile on win32 (not sure which<br>
> > compiler though, it might be MSVC only), so this might be a hurdle for step<br>
> > 1).<br>
> ><br>
> > So what is the plan in details?<br>
> ><br>
><br>
> Maybe <a href="http://www.openjpeg.org/" target="_blank">http://www.openjpeg.org/</a> is a better match, BSD license... But it's<br>
> huge.<br>
<br>
</div></div>The Mantis entry has links to the earlier discussions, so there is a good<br>
summary of the issues there. I do not know what the detailed plan should be<br>
but I think that we need two things:<br>
<br>
1) Some platforms, probably including some unix platforms, need to use the<br>
old jpeg library code that we keep in platforms/Cross/plugins/JPEGReadWriter2Plugin.<br>
This must continue to work for the platforms that require it.<br>
<br>
2) Other platforms, especially Linux distributions, would prefer to link<br>
directly to the jpeg runtime library provided by the operating system.<br>
<br>
There should be no GPL issues because linking to a runtime libjpeg is no<br>
different from linking to any other runtime library on Linux.<br>
<br></blockquote><div><br></div><div>Beware, this is why LGPL was created for, no?<br>But GPL is different from LGPL.</div><div>I don't feel like reading those licenses again, it's just too boring, so someone should confirm that:<br>
link with GPL and you become GPL, it's viral.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
It may be that the best way to achieve this is to provide different variants<br>
of jpeg plugin in VMMaker. But I have not looked at this in detail, so I<br>
cannot say what is the best approach.<br>
<br>
Dave<br>
<br>
<br>
</blockquote></div><br></div></div>