Re: [Development] Retiring libtiff too

2016-05-03 Thread Shawn Rutledge
> On 3 May 2016, at 08:39, Lars Knoll wrote: > Ideally, I would like to get rid of these libraries in src/3rdparty. Instead, > we should build up to date versions of these libs in Coin, and simply ship > those together with our Qt libraries. With the online installers it should in > the longer

Re: [Development] Retiring libtiff too

2016-05-03 Thread Shawn Rutledge
> On 3 May 2016, at 08:39, Lars Knoll wrote: > Ideally, I would like to get rid of these libraries in src/3rdparty. Instead, > we should build up to date versions of these libs in Coin, and simply ship > those together with our Qt libraries. With the online installers it should in > the longer

Re: [Development] Retiring libtiff too

2016-05-03 Thread Thiago Macieira
Em terça-feira, 3 de maio de 2016, às 07:06:41 PDT, Lars Knoll escreveu: > On 03/05/16 08:58, "Development on behalf of Thiago Macieira" > thiago.macie...@intel.com> wrote: > > >Em terça-feira, 3 de maio de 2016, às 06:39:42 PDT, Lars Knoll escreveu: > > > >> Ideally, I would like to get rid of

Re: [Development] Retiring libtiff too

2016-05-03 Thread Lars Knoll
On 03/05/16 08:58, "Development on behalf of Thiago Macieira" wrote: >Em terça-feira, 3 de maio de 2016, às 06:39:42 PDT, Lars Knoll escreveu: >> Ideally, I would like to get rid of these libraries in src/3rdparty. >> Instead, we should build up to date versions of these libs in Coin, and >> si

Re: [Development] Retiring libtiff too

2016-05-02 Thread Thiago Macieira
Em terça-feira, 3 de maio de 2016, às 06:39:42 PDT, Lars Knoll escreveu: > Ideally, I would like to get rid of these libraries in src/3rdparty. > Instead, we should build up to date versions of these libs in Coin, and > simply ship those together with our Qt libraries. With the online > installers

Re: [Development] Retiring libtiff too

2016-05-02 Thread Lars Knoll
On 02/05/16 20:20, "Development on behalf of Thiago Macieira" wrote: >On segunda-feira, 2 de maio de 2016 18:07:29 PDT Lars Knoll wrote: >> >> So while I don't like us having copies of these libraries in our >> >> repositories, not shipping any support for these image formats in our >> >> packa

Re: [Development] Retiring libtiff too

2016-05-02 Thread Thiago Macieira
On sexta-feira, 29 de abril de 2016 21:14:17 PDT Allan Sandfeld Jensen wrote: > Do you have any citations for these issues? CVE-2014-9655 CVE-2015-1547 CVE-2015-8665 CVE-2015-8683 CVE-2015-7554 CVE-2015-8668 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open So

Re: [Development] Retiring libtiff too

2016-05-02 Thread Thiago Macieira
On segunda-feira, 2 de maio de 2016 18:07:29 PDT Lars Knoll wrote: > >> So while I don't like us having copies of these libraries in our > >> repositories, not shipping any support for these image formats in our > >> packages is not a good option neither. > > > >I kinda disagree. I would prefer an

Re: [Development] Retiring libtiff too

2016-05-02 Thread Lars Knoll
On 02/05/16 17:52, "Development on behalf of Thiago Macieira" wrote: >On segunda-feira, 2 de maio de 2016 10:46:53 PDT Lars Knoll wrote: >> Well, on Linux these libraries are nicely available on the system. But it >> does not help us on Windows, where we do have to ship these libraries if we >

Re: [Development] Retiring libtiff too

2016-05-02 Thread Thiago Macieira
On segunda-feira, 2 de maio de 2016 10:46:53 PDT Lars Knoll wrote: > Well, on Linux these libraries are nicely available on the system. But it > does not help us on Windows, where we do have to ship these libraries if we > want to provide something that's easy to use for our users/customers. Let m

Re: [Development] Retiring libtiff too

2016-05-02 Thread Lars Knoll
On 30/04/16 12:22, "Development on behalf of Richard Moore" mailto:development-bounces+lars.knoll=qt...@qt-project.org> on behalf of r...@kde.org> wrote: On 29 April 2016 at 20:14, Allan Sandfeld Jensen mailto:k...@carewolf.com>> wrote: On Friday 29 April 2016, Thiago Mac

Re: [Development] Retiring libtiff too

2016-05-01 Thread Thiago Macieira
On sábado, 30 de abril de 2016 11:22:37 PDT Richard Moore wrote: > ​Isn't commonly used on the web, and can't be used on the web are > different. Do we have code that prevents such usage? I'm not aware we even > have an API to limit the set of image format plugins that would get loaded. You may re

Re: [Development] Retiring libtiff too

2016-04-30 Thread Richard Moore
On 29 April 2016 at 20:14, Allan Sandfeld Jensen wrote: > On Friday 29 April 2016, Thiago Macieira wrote: > > See https://lists.clearlinux.org/pipermail/dev/2016-April/000290.html > > > > This is yet another reason we have to stop bundling third party > components, > > especially the image and mo

Re: [Development] Retiring libtiff too

2016-04-29 Thread Allan Sandfeld Jensen
On Friday 29 April 2016, Thiago Macieira wrote: > See https://lists.clearlinux.org/pipermail/dev/2016-April/000290.html > > This is yet another reason we have to stop bundling third party components, > especially the image and movie formats. > > So I recommend dropping the libtiff 3rdparty compon

[Development] Retiring libtiff too

2016-04-29 Thread Thiago Macieira
See https://lists.clearlinux.org/pipermail/dev/2016-April/000290.html This is yet another reason we have to stop bundling third party components, especially the image and movie formats. So I recommend dropping the libtiff 3rdparty component and keep the plugin for when the system library is fou