From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez installs alsa related stuff under /etc/alsa instead of /usr/share/alsa
Date: Fri, 05 Mar 2010 10:11:35 +0100 [thread overview]
Message-ID: <1267780295.6970.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1267753367.29510.26.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
El jue, 04-03-2010 a las 17:42 -0800, Marcel Holtmann escribió:
> Hi Pacho,
>
> > bluez installs stuff into /etc/alsa and it seems wrong since default
> > location for alsa stuff seems to be /usr/share/alsa instead. You can
> > also see that this is been workarounded in ubuntu, gentoo (and probably
> > debian also).
> >
> > Any reason why using /etc/alsa instead?
>
> I thought that is the default location. If that is wrong, then please
> quote the ALSA documentation and send a patch to fix it.
>
> Regards
>
> Marcel
alsa-lib configure.in seems to indicate that /usr/share/alsa is the
default one:
dnl ALSA configuration directory
AC_ARG_WITH(configdir,
AS_HELP_STRING([--with-configdir=dir],
[path where ALSA config files are stored]),
confdir="$withval", confdir="")
if test -z "$confdir"; then
eval dir="$datadir"
case "$dir" in
/*) ;;
*) dir="$prefix/share"
esac
confdir="$dir/alsa"
fi
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-05 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 8:37 bluez installs alsa related stuff under /etc/alsa instead of /usr/share/alsa Pacho Ramos
2010-03-05 1:42 ` Marcel Holtmann
2010-03-05 9:11 ` Pacho Ramos [this message]
2010-03-05 9:24 ` Pacho Ramos
2010-04-10 11:28 ` Pacho Ramos
2010-07-16 10:40 ` Pacho Ramos
2010-07-16 17:01 ` Johan Hedberg
2010-07-16 17:21 ` Pacho Ramos
2010-07-16 18:08 ` Gustavo F. Padovan
2010-07-16 18:46 ` Pacho Ramos
2010-07-16 23:44 ` Johan Hedberg
2010-07-17 14:09 ` Pacho Ramos
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=1267780295.6970.5.camel@localhost.localdomain \
--to=pacho@condmat1.ciencias.uniovi.es \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).