projectm-devel

[projectM-devel] sysconfdir

[Hai Z. <ha...@gm...>]

First of all, Peter, thank you for opening mailing list. I hope you
find it useful :). I'll think I'll forward all my xmms-project related
correspondence for sake of history.

Quote from forum:
--------------------------
The problem with sysconfdir is just that I feel weird putting
/usr/local/etc on people's computer just for projectM's config file.
My personal experience is that very few packages use /usr/local/etc
with default options.

Anyway, to solve the problem I put the default config file into
$DATADIR. ~/.projectM/ is created at runtime if necessary, and the
config file is copied there. So the copy of the config in DATADIR is
only used when creating ~/.projectM.

I'm going to try and do something with ~/.projectM/presets. Maybe we
should have that conversation on the mailing list.
--------------------------
What ever you are happy with :)
Just have in mind that you will have same config file replicated over
all of the user  home directories and although now its only about 1k,
its not good as a strategy.
But again, currently its cost-effective, and again what ever you are
happy with :)

Best.
--
Zaar

Re: [projectM-devel] sysconfdir

[n0dalus <n0d...@gm...>]

On 4/25/06, Hai Zaar <ha...@gm...> wrote:
> Anyway, to solve the problem I put the default config file into
> $DATADIR. ~/.projectM/ is created at runtime if necessary, and the
> config file is copied there. So the copy of the config in DATADIR is
> only used when creating ~/.projectM.

I think this is a good solution.

> I'm going to try and do something with ~/.projectM/presets. Maybe we
> should have that conversation on the mailing list.

We could get projectM to search $DATADIR/presets as well as
~/.projectM/presets when looking for files. If the inbuilt editing
interface is ever made a bit more useful (at the moment in
xmms-projectM it is about 90% broken), we could also use the per-user
path to store saved/edited presets.

> Just have in mind that you will have same config file replicated over
> all of the user  home directories and although now its only about 1k,
> its not good as a strategy.

We could have the one in $HOME just contain some small text about how
$DATADIR/... contains the default settings and that these can be
overridden using this file.

Speaking of config files though, maybe we should move to using
key/value pairs instead of just lines needing to be in a specific
order. That also makes being able to override values simpler.

Once we get this in place, we can make the 'Configure' button in xmms
do something actually useful and provide an interface to edit the
options.

n0dalus.