Re: [Gimp-developer] New GIMP configure warning/error

Hi, On Wed, Jul 5, 2017 at 9:27 PM, Kristian Rietveld wrote: > >> On 13 May 2017, at 15:21, Jehan Pagès wrote: >>> A potential solution could be to write a Mac-specific GIO TLS backend that >>> depends on macOS system libraries which can be

Re: [Gimp-developer] New GIMP configure warning/error

> On 13 May 2017, at 15:21, Jehan Pagès wrote: >> A potential solution could be to write a Mac-specific GIO TLS backend that >> depends on macOS system libraries which can be shipped instead of the >> default TLS backend that depends on gnutls. > > Of course, this

Re: [Gimp-developer] New GIMP configure warning/error

Hi, Since I'm not sure to which mail to reply, I'll reply to the thread's original mail... I'll keep it short: - additional dependency: Í could not care less about some more MB to build/install/distribute in order to get whatever feature. - networking code: that's a tough one, we are

Re: [Gimp-developer] New GIMP configure warning/error

> Am 13.05.2017 um 15:50 schrieb Jehan Pagès : > > > We have a few issues with our webkit internal browser, one of them is > that we still use an old webkit version (because of GTK+2; newer > versions are for GTK+3), which is therefore deprecated. Security wise, >

Re: [Gimp-developer] New GIMP configure warning/error

Hi, On Sat, May 13, 2017 at 3:40 PM, Partha Bagchi wrote: > > > On Sat, May 13, 2017 at 8:52 AM, Jehan Pagès > wrote: >> >> Hi, >> >> On Sat, May 13, 2017 at 6:25 AM, Partha Bagchi wrote: >> > >> > >> >> >> No, there are at

Re: [Gimp-developer] New GIMP configure warning/error

Hi, On Sat, May 13, 2017 at 3:15 PM, Pat David wrote: > Is it not possible to invoke the default browser and hand off the https > responsibility to it? That's definitely a possibility, and even a good one IMO. We have a few issues with our webkit internal browser, one of

Re: [Gimp-developer] New GIMP configure warning/error

Hi, On Thu, May 11, 2017 at 8:53 PM, Partha Bagchi wrote: > On Thu, May 11, 2017 at 2:49 PM, Alexandre Prokoudine < > alexandre.prokoud...@gmail.com> wrote: > >> On Thu, May 11, 2017 at 9:34 PM, Partha Bagchi wrote: >> >> > I am perplexed to see that we need glib-networking

Re: [Gimp-developer] New GIMP configure warning/error

On Thu, May 11, 2017 at 9:53 PM, Partha Bagchi wrote: >> warnings on HTTP websites. Also the experience will be significantly >> degraded without SSL/TLS support since the help browser will fail to >> load the manual remotely, and opening various remote files on secure >> protocols will fail.

Re: [Gimp-developer] New GIMP configure warning/error

Hi, On Thu, May 11, 2017 at 8:34 PM, Partha Bagchi wrote: > I am getting the following warning: > >> WARNING: Your GTK+ version is 2.24.31. >> The recommended GTK+ version under Windows is 2.24.32 or over. >> If you continue without updating GTK+, shortcuts

Re: [Gimp-developer] New GIMP configure warning/error

On Thu, May 11, 2017 at 2:49 PM, Alexandre Prokoudine < alexandre.prokoud...@gmail.com> wrote: > On Thu, May 11, 2017 at 9:34 PM, Partha Bagchi wrote: > > > I am perplexed to see that we need glib-networking suddenly since my git > > pull from a couple of days ago? Is there a reason to requiring

Re: [Gimp-developer] New GIMP configure warning/error

On Thu, May 11, 2017 at 9:34 PM, Partha Bagchi wrote: > I am perplexed to see that we need glib-networking suddenly since my git > pull from a couple of days ago? Is there a reason to requiring glib > networking support? To quote from

[Gimp-developer] New GIMP configure warning/error

I am getting the following warning: > WARNING: Your GTK+ version is 2.24.31. > The recommended GTK+ version under Windows is 2.24.32 or over. > If you continue without updating GTK+, shortcuts won't work with > non-latin locales, and vector icons will be disabled.