From: Alain Kalker <a.c.kalker@gmail.com>
To: alsa-devel@alsa-project.org
Subject: [BUG] src/conf/alsa.conf: Hard-coded path `/etc/asound.conf`, needs `@func sysconfdir`.
Date: Sun, 5 Mar 2017 19:17:55 +0100 [thread overview]
Message-ID: <a844ffab-3a8b-bc92-9296-0554682553cf@gmail.com> (raw)
The file `src/conf/alsa.conf` contains the hard-coded path
`/etc/asound.conf`, which in some use cases may not be correct.
One particular use case: Termux[1], a "Linux subsystem for Android",
plans to use ALSA plugins to communicate with the OpenSL ES
implementation in Android. In doing so, it needs to not conflict with
any vendor provided ALSA implentation, which could conceivably use an
`/etc/asound.conf` of its own. At any rate, the system `/etc` directory
is normally not writable by non-root users of Android.
I would suggest adding a `snd_func_sysconfdir` in `src/confmisc.c
(analogous to `snd_func_datadir`) so packagers and users can place a
global `asound.conf` file in a directory to which they have write access
and which doesn't conflict with the systems ALSA.
The desired path can already be specified at build time by using
`./configure --sysconfdir=<dir>`, which conveniently defaults to
PREFIX/etc in any case. It is available as configure variable:
`sysconfdir='${prefix}/etc'`, and only needs to be substituted to be
available to `src/confmisc.c`.
Kind regards,
Alain Kalker
[1]: https://termux.com/
next reply other threads:[~2017-03-05 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 18:17 Alain Kalker [this message]
2017-03-20 12:46 ` [BUG] src/conf/alsa.conf: Hard-coded path `/etc/asound.conf`, needs `@func sysconfdir` 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=a844ffab-3a8b-bc92-9296-0554682553cf@gmail.com \
--to=a.c.kalker@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).