[KDE/Mac] Thoughts on standard directories in Qt5 - QStandardPaths

[Ian Wadham]

Hi Jeremy,

On 12/12/2014, at 1:45 AM, Jeremy Whiting wrote:
> QCoreApplication gets the organization name and application name from whatever we tell it. Look at http://quickgit.kde.org/?p=kanagram.git&a=blob&h=94effa89abfe69f50ea0888bb2c8b99564130166&hb=57783ce14365e087573930cb9dff4ed948c4c190&f=src%2Fmain.cpp for example in the KF5 porting notes it suggests setting the application name and organization name when porting from KApplication to QApplication so it can use those values in other things like KConfig and such I think.

That code is actually setting "organizationDomain" --- to "kde.org".  QSP will
use this as part of its <APPNAME> string, IFF "organizationName" is not set,
prepending it to the *application* name (kanagram, in this case).

I was talking about setting "organizationName" (not "organizationDomain")
to "a unique name generated at packaging", i.e. externally to the application's
code and in order to do something "MacPorts-ish".  But then we don't have
KApplication any more… ;-)

I hope I am not getting paranoid, but I wonder if some KDE apps will be looking
for their data files (DataLocation) in subdir "kde.org/foo" and some in subdir "foo",
depending on whether the "foo" maintainer called setOrganizarionDomain()… :-(

Another thing that may hit us (and maybe MacPorts in general) a year or so down
the track is a little item on OS X called "taskgated" (see "man taskgated").  In effect,
I think it gives one process "permission" to run another process, depending on
what organization is the provider of the process.  At present, MacPorts bypasses
this check by using the OS X Tiger settings, from years ago, but my guess is that,
sooner or later, Apple will discontinue those settings, as part of their ongoing
tightening of security.  Well, as I say, it's not happening now, so why worry?

Cheers, Ian W.