XDG Part Deux

As with the previous post, this pertains solely to *nix (primarily Linux and Mac OS X) users. Windows users are warned to avert their eyes to avoid irreversible Unixification.

I’m not a fan of pushing maintenance duty onto end-users, so I’ve done some work to automate the XDG configuration update process bobbens mentioned.

When first running the next release, if old configuration files exist (in ye olde ~/.naev) a prompt will show up, offering to automatically invoke the update script. This will hopefully reduce the process down to simply clicking “Yes” for most users.

Of course, you’re welcome to click “No”, as well. To hopefully handle all distribution cases (whether Naev is run from loose files in a Git checkout, installed via a package manager or grabbed directly from SourceForge) the script is both included in the single-file ndata and available as a standalone file.

With any luck, the configuration update will be smooth and painless. It should also make the coming release less painful for bobbens, because I think if we’d gone the full-manual route and asked package maintainers to correctly run the script for each user, they’d be demanding his head on a pike.

Share on RedditTweet about this on TwitterShare on Google+Share on FacebookShare on StumbleUponEmail this to someone

4 comments to XDG Part Deux

  • DarthKev

    I like how you missed the ‘U’ and hit ‘8’ getting an asterisk at the front of Unix.

    All of this pretty much goes over my head, but at least I understand the part about the change being made easy for users. Now I just need to find a way to sit patiently and wait for the next release…

  • Simon

    DarthKev: *nix is a sort of obscure way to refer to any OS that is either derived from the original Unix (rare nowadays except in business environments), or a clone of it (Linux, OS X, and the BSDs). It may not seem to make sense now, but in the past, some Unix variants had names like Xenix or AIX, which fit the pattern.

  • pike


    Just curious – what are some of the good reasons to move to XDG layout?

  • Deiz

    Standardization’s rarely bad. I find the split-up XDG dirs to be a bit clunky in practice, but they’re far more flexible than a single-dir approach.

    Importantly, the split is consistent between applications. For example, you could stick $HOME on a spinning-platter hard drive, but mount ~/.cache/ from a SSD, potentially speeding up XDG-compliant programs.

Leave a Reply




You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>