Base Directory Specification and plugins

Gary Kramlich grim at
Sat Nov 20 18:15:27 PST 2010

I'm working on an application where I want to allow user plugins.
However, while trying to follow the Base Directory specification, I
realized that this seems to be overlooked in the specification.

What I mean here, is that neither the cache, config, or data directories
seem to be the correct place to put a native plugin.

Obviously config is out right away since it's not configuration data,
and cache is out since a plugin isn't necessarily non-essential.

That leaves the data directory.  However, the data directory on a unix
machine ends up being ~/.local/share and putting a native plugin under a
share directory seems to be completely wrong to me.

What I'm purposing is a XDG_LIBRARY_DIR which would point to
~/.local/lib and have an XDG_LIBRARY_DIRS counterpart that would list
off /usr/lib, /usr/local/lib, and so on.

I have no idea if this is the best solution, but look forward to any
comments about how to fix my problem while following the specification.


Gary Kramlich <grim at>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the xdg mailing list