alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
* [BUG] src/conf/alsa.conf: Hard-coded path `/etc/asound.conf`, needs `@func sysconfdir`.
@ 2017-03-05 18:17 Alain Kalker
  2017-03-20 12:46 ` Takashi Iwai
  0 siblings, 1 reply; 2+ messages in thread
From: Alain Kalker @ 2017-03-05 18:17 UTC (permalink / raw)
  To: alsa-devel

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [BUG] src/conf/alsa.conf: Hard-coded path `/etc/asound.conf`, needs `@func sysconfdir`.
  2017-03-05 18:17 [BUG] src/conf/alsa.conf: Hard-coded path `/etc/asound.conf`, needs `@func sysconfdir` Alain Kalker
@ 2017-03-20 12:46 ` Takashi Iwai
  0 siblings, 0 replies; 2+ messages in thread
From: Takashi Iwai @ 2017-03-20 12:46 UTC (permalink / raw)
  To: Alain Kalker; +Cc: alsa-devel

On Sun, 05 Mar 2017 19:17:55 +0100,
Alain Kalker wrote:
> 
> 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`.

Maybe an easier fix would be to replace it from
src/conf/alsa.conf.in.


Takashi

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-03-20 12:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-05 18:17 [BUG] src/conf/alsa.conf: Hard-coded path `/etc/asound.conf`, needs `@func sysconfdir` Alain Kalker
2017-03-20 12:46 ` Takashi Iwai

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).