From: Jaroslav Kysela <perex@perex.cz>
To: gmane@colin.guthr.ie
Cc: Colin Guthrie <colin@mageia.org>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] conf: Allow for a directory to be given as a config file.
Date: Mon, 12 Sep 2011 08:57:42 +0200 [thread overview]
Message-ID: <4E6DAD66.3080204@perex.cz> (raw)
In-Reply-To: <1315744838-21911-2-git-send-email-gmane@colin.guthr.ie>
Date 11.9.2011 14:40, gmane@colin.guthr.ie wrote:
> From: Colin Guthrie <colin@mageia.org>
>
> When this is done, *.conf files can be placed in that directory and they
> will be processed by as if they were included directly.
>
> A directory (typically /usr/share/alsa/alsa.conf.d/) has been
> added into the distribution.
Thanks for this patch.
> +@hooks [
> + {
> + func load
> + files [
> + "@ALSA_CONFIG_DIR@/alsa.conf.d/"
I think that it might be more flexible and analogical to keep the
original configuration file and implement the confdir function - see the
datadir example.
Implemented:
"{ @func datadir }"
To be added:
"{ @func confdir }"
See snd_func_datadir() in confmisc.c.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2011-09-12 6:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 12:40 Allow alsa configuration to be loaded from a alsa.conf.d folder gmane
2011-09-11 12:40 ` [PATCH] conf: Allow for a directory to be given as a config file gmane
2011-09-12 6:57 ` Jaroslav Kysela [this message]
2011-09-12 8:23 ` Colin Guthrie
2011-09-12 8:27 ` Takashi Iwai
2011-09-13 21:00 ` Colin Guthrie
2011-09-13 21:03 ` Allow alsa configuration to be loaded from a alsa.conf.d folder v2 gmane
2011-09-13 21:04 ` [PATCH] conf: Allow for a directory to be given as a config file gmane
2011-09-16 6:51 ` Takashi Iwai
2011-09-16 8:28 ` Colin Guthrie
-- strict thread matches above, loose matches on Subject: below --
2011-09-16 9:04 gmane
2011-09-20 8:09 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E6DAD66.3080204@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=colin@mageia.org \
--cc=gmane@colin.guthr.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.