Change in qt/qtbase[dev]: QStandardPaths: Add XDG_CONFIG_DIRS and XDG_DATA_DIRS paths ...

[Bradley Giesbrecht]

On Jan 14, 2015, at 6:53 AM, René J.V. Bertin <rjvbertin at gmail.com> wrote:

> On Wednesday January 14 2015 14:44:12 Jeremy Whiting wrote:
>> Jeremy Whiting has posted comments on this change.
> 
> Jeremy, could you summarise the changes please?
> 
>> 
>> Change subject: QStandardPaths: Add XDG_CONFIG_DIRS and XDG_DATA_DIRS paths on OSX.
>> ......................................................................
>> 
>> 
>> Patch Set 3:
>>> What is the intended way of deploying and running a KDE application on Mac
>>> OS X?
>>> 
>>> One way that I can see is to create real bundles. So if Kate uses
>>> kf5-karchive, it would include this and other frameworks it needs in its
>>> own bundle. The application would be entirely self-contained and there
>>> would be no relevance for any XDG environment variables AFAICS. I
>>> personally think this is a good way of deploying applications, because it
>>> is very user friendly.
>>> 
>>> Another way that I can see is through frameworks like (home)brew, where
>>> each
>>> application will end up in its own prefix, right? (something like
>>> /usr/local/Cellar/Kate/5.0/...) How would frameworks cooperate with
>>> cellars
>>> and how would any environment variables - that are required for running -
>>> be set? Is this something the user would have to do in the terminal?> > 
>> Simon,
>> 
>> Exactly, there are two ways, one including all libraries and data files within the .app itself, and two, using homebrew/fink/macports to install the application and it's dependencies. From what I've seen with macports you set your prefix and it adds environment variables to your user's startup script (.profile iirc) so the prefix you set is initialized by the homebrew/fink/macports setup itself.
> 
> It's been a while since I installed MacPorts from scratch, and I don't think it ever actually modified my startup script, but in principle you only need to add /opt/local/bin (or ${prefix}/bin) to your path.

If you install MacPorts from the binary installer a postflight script [1] is run which does/can set vars in .profile; while installing from source leaves the task of env modification to the user.

[1] https://guide.macports.org/chunked/installing.shell.html#installing.shell.postflight


Regards,
Bradley Giesbrecht (pixilla)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150114/27f48318/attachment.sig>