[Development] Adding new third party component three.js to Qt?

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 14 January 2015 09:24:43 Thiago Macieira wrote:
> On Wednesday 14 January 2015 11:38:55 Lisandro Damián Nicanor Pérez Meyer
> 
> wrote:
> > The same can be said about C/C++ 3rdparty libraries. So no, bundling is
> > not
> > good for distros. Imagine a security bug appears: we need to start hunting
> > down each embedded version and fix it, checking that we don't break
> > anything specially in forked cases. A nightmare.
> 
> Actually, the problem here is not that of shipping a bundled version. It's
> embedding the binary inside one of Qt binaries.
> 
> Let's solve this problem first: how to find the JS file (minified or not)
> somewhere on disk, without Qt resources. Once that is solved, distros can
> opt to build three.js from the official sources and apply the necessary Qt
> patches in the manner that is most helpful to them.

This would indeed be a nice way to start fixing this. I might be becoming mad, 
but I'll see what can be done in that regard (we do have a policy for that, 
but so far Debian-only as far as I know).

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150116/65ab729b/attachment.sig>