On Wednesday November 11 2015 20:37:36 Petroules Jake wrote:
> What we SHOULD have in Qt is something similar to NSSearchPathDomainMask so
> we could have a little more fine grained control. Maybe a user WANTS to write
> to locations in the local domain instead of the user domain (and in some
>
On Nov 11, 2015, at 12:21 PM, David Faure mailto:fa...@kde.org>>
wrote:
On Wednesday 11 November 2015 19:09:58 Petroules Jake wrote:
Feel free to do whatever you like for test mode but do not change the existing
writable paths.
Jake, I would like to understand why you say that. As the QSP auth
On Wednesday 11 November 2015 19:09:58 Petroules Jake wrote:
> Feel free to do whatever you like for test mode but do not change the
> existing writable paths.
Jake, I would like to understand why you say that. As the QSP author and
maintainer,
I am 100% sure that the value of writableLocation(x
On Nov 11, 2015, at 8:20 AM, René J.V. Bertin
mailto:rjvber...@gmail.com>> wrote:
On Wednesday November 11 2015 16:03:31 Petroules Jake wrote:
I don't understand, what do you mean with "there is only one location"?
I mean the API returns a single value, not a list. However, READable locations
On Wednesday November 11 2015 19:07:17 David Faure wrote:
> Yes, and the value returned by writableLocation() is supposed to be
> user-specific
> (something under $HOME) rather than system-wide.
Agreed.
>
> So /Applications should be in QSP::standardLocations(ApplicationsLocation)
> but QSP::w
On Wednesday 11 November 2015 16:03:31 Petroules Jake wrote:
> I mean the API returns a single value, not a list.
Yes, and the value returned by writableLocation() is supposed to be
user-specific
(something under $HOME) rather than system-wide.
So /Applications should be in QSP::standardLocatio
On Nov 11, 2015, at 7:13 AM, René J.V. Bertin
mailto:rjvber...@gmail.com>> wrote:
On Wednesday November 11 2015 15:52:33 David Faure wrote:
Cross-posting on Qt's development ML because it seems more than relevant there.
To put things in context: this discussion on kde-frameworks-devel was star
On Nov 11, 2015, at 7:53 AM, René J.V. Bertin
mailto:rjvber...@gmail.com>> wrote:
On Wednesday November 11 2015 15:32:20 Petroules Jake wrote:
No, there is only one location so it must remain /Applications as expected by
anyone on the OS X platform.
I don't understand, what do you mean with "
On Wednesday November 11 2015 16:03:31 Petroules Jake wrote:
>I don't understand, what do you mean with "there is only one location"?
>
>I mean the API returns a single value, not a list. However, READable locations
>will return a list containing both $HOME/Applications and /Applications
Ah. I h
On Wednesday November 11 2015 15:32:20 Petroules Jake wrote:
>No, there is only one location so it must remain /Applications as expected by
>anyone on the OS X platform.
I don't understand, what do you mean with "there is only one location"?
It is also expected that regular users do not have wr
On Wednesday November 11 2015 15:52:33 David Faure wrote:
Cross-posting on Qt's development ML because it seems more than relevant there.
To put things in context: this discussion on kde-frameworks-devel was started
because an autotest from KService deleted a good chunk from my /Applications
di
On Wednesday 11 November 2015 15:45:49 René J.V. Bertin wrote:
> On Wednesday November 11 2015 14:49:57 David Faure wrote:
>
> > qstandardpaths_mac.mm says
> > QString QStandardPaths::writableLocation(StandardLocation type)
> > {
> > if (isTestModeEnabled()) {
> > const QString qttestD
12 matches
Mail list logo
