Please support looking up config file from multiple paths, each overriding the other, preferrably using the XDG standard as implemented in the dirs crate.
Concretely I have packaged alumet for Debian, where I most possible plugins are built and provided system-wide, but enabling them all by default does not provide the best user experience. Notably the nvml plugin depends on loading a shared library which Debian does not install by default (it is offered in what we in Debian call the "contrib" area) because it links against other libraries which Debian consider non-free (our "non-free" area).
That is just mentioned here as an example. Concretely that issue could be solved in other ways, my point here is that the system administrator may want to offer a set of default settings that each user then may derive from.
Please support looking up config file from multiple paths, each overriding the other, preferrably using the XDG standard as implemented in the
dirscrate.Concretely I have packaged alumet for Debian, where I most possible plugins are built and provided system-wide, but enabling them all by default does not provide the best user experience. Notably the nvml plugin depends on loading a shared library which Debian does not install by default (it is offered in what we in Debian call the "contrib" area) because it links against other libraries which Debian consider non-free (our "non-free" area).
That is just mentioned here as an example. Concretely that issue could be solved in other ways, my point here is that the system administrator may want to offer a set of default settings that each user then may derive from.