Re: QStandardPaths::GenericDataLocation on MacOS

Hi, I just remembered that some time ago I wrote a small library that allows me to use binaries compiled against my own patched qt5-kde with an "official" Qt build: it provides the additional symbols that are in qt5-kde but not standard Qt through code injection (DYLD_INSERT_LIBRARIES). That

Re: QStandardPaths::GenericDataLocation on MacOS

I'll shuffle the bits in this mail a bit, in an attempt to get the discussion back to the main topic (or at least the thing that I intended to be the main topic): On Thu, 03 May 2018 23:11:56 +0200 René J.V. Bertin wrote: > On Thursday May 03 2018 21:57:03 Thomas

Re: QStandardPaths::GenericDataLocation on MacOS

On Thu, 03 May 2018 21:09:03 +0200 René J.V. Bertin wrote: > >On Fri, May 4, 2018 at 2:38 AM, Thomas Friedrichsmeier > > >> homebrew, craft). It is also about the fact that this installation > >> option causes problems, e.g. if users are to mix MacPorts and a > >>

Re: QStandardPaths::GenericDataLocation on MacOS

On Thursday May 03 2018 21:57:03 Thomas Friedrichsmeier wrote: > _If_ applications were to actually install to the current paths defined > for that on Mac "Library/Application Support", and "~Library/Application > Support", on more, no less, _then_ clashes would start to happen. As A priori no,

Re: QStandardPaths::GenericDataLocation on MacOS

Hi, > On Fri, May 4, 2018 at 2:38 AM, Thomas Friedrichsmeier > wrote: >> Hi, >> >> On Thu, 03 May 2018 16:01:46 +0200 >> René J.V. Bertin wrote: >>> On Thursday May 03 2018 15:19:33 Thomas Friedrichsmeier wrote: >>> >plan is

Re: QStandardPaths::GenericDataLocation on MacOS

>On Fri, May 4, 2018 at 2:38 AM, Thomas Friedrichsmeier >> homebrew, craft). It is also about the fact that this installation >> option causes problems, e.g. if users are to mix MacPorts and a >> single-app-bundled KF5 app No, that shouldn't happen, and it doesn't with the official Kate bundle.

Re: QStandardPaths::GenericDataLocation on MacOS

On Fri, May 4, 2018 at 2:38 AM, Thomas Friedrichsmeier wrote: > Hi, > > On Thu, 03 May 2018 16:01:46 +0200 > René J.V. Bertin wrote: >> On Thursday May 03 2018 15:19:33 Thomas Friedrichsmeier wrote: >> >plan is actually to get David

Re: QStandardPaths::GenericDataLocation on MacOS

Hi, I'll just answer a few select points, because, yes I am aware this has a tiny bit of a history, and I don't want to see a repeat. The master plan is actually to get David Faure to champion a solution (whichever one) into Qt. So before getting lost in the detail of the various approaches, I'd

Re: QStandardPaths::GenericDataLocation on MacOS

Hi, On Thu, 03 May 2018 16:01:46 +0200 René J.V. Bertin wrote: > On Thursday May 03 2018 15:19:33 Thomas Friedrichsmeier wrote: > >plan is actually to get David Faure to champion a solution (whichever > >one) into Qt. > > I can be wrong, but I don't see that happening

Re: QStandardPaths::GenericDataLocation on MacOS

On Thursday May 03 2018 15:19:33 Thomas Friedrichsmeier wrote: Hi, >plan is actually to get David Faure to champion a solution (whichever >one) into Qt. I can be wrong, but I don't see that happening beyond his general support. Also, what are the chances that this will be overhauled anyway for

Re: QStandardPaths::GenericDataLocation on MacOS

On Thursday May 03 2018 22:22:30 Ben Cooksley wrote: Hi, > Last time around the Qt Core maintainer vetoed our attempts to get > this changed, and forced us to liase with a Qt Company employee whose > responsiveness was lacking (to say the least). Suffice to say, that > effectively killed the

Re: QStandardPaths::GenericDataLocation on MacOS

On Thu, May 3, 2018 at 8:02 PM, Thomas Friedrichsmeier wrote: > Hi! Hi all, > > Quick summary, first: > KF5 relies on storing data in QStandardPaths::GenericDataLocation, but > that location is problematic on Mac because it refers to absolute, >

QStandardPaths::GenericDataLocation on MacOS

Hi! Quick summary, first: KF5 relies on storing data in QStandardPaths::GenericDataLocation, but that location is problematic on Mac because it refers to absolute, non-customizable system paths, only. We'd like to avoid patching Qt, so we are looking to come up with a solution that has a chance

Re: QStandardPaths::GenericDataLocation on MacOS

On Thursday May 03 2018 10:02:35 Thomas Friedrichsmeier wrote: Hi, I have mostly skimmed over your long email but allow me to warn you firsthand that I've tried to get feedback and constructive collaboration like this before and never got very far because the prevailing attitude is 1) don't