Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: ALSA development <alsa-devel@alsa-project.org>,
	pkg-alsa-devel@lists.alioth.debian.org
Subject: Re: [PATCH] alsa-utils 1.0.27.1 still ships 90-alsa-restore.rules
Date: Thu, 30 May 2013 20:44:47 +0200	[thread overview]
Message-ID: <51A79E1F.9070200@perex.cz> (raw)
In-Reply-To: <20130530150631.GA20416@galadriel.home.lxtec.de>

Date 30.5.2013 17:06, Elimar Riesebieter wrote:
> * Jaroslav Kysela <perex@perex.cz> [2013-05-30 15:55 +0200]:
> 
>> Date 30.5.2013 15:08, Elimar Riesebieter wrote:
>>>
>>> Hi all,
>>>
>>> [0] tells:
>>> alsactl: remove 90-alsa-restore.rules from the tar ball
>>>
>>> but it still ships 90-alsa-restore.rules.in and installs the file as
>>> 90-alsa-restore.rules
>>
>> It's correct. The rules file should be generated after configure/make
>> with correct paths.
>>
>> It's not a complete removal of this feature. You probably miss this fix:
>>
>> http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=c0f70a0b8e340d6ee903ff226886bb6f969d46a1
> 
> Well, it is useless when EPREFIX (i.e /usr) isn't mounted while udev runs?

The distro should handle this situation.

> It should be better to restore mixer settings by an initscript.

It does not work for plug and play devices.

						Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.

      reply	other threads:[~2013-05-30 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 13:08 [PATCH] alsa-utils 1.0.27.1 still ships 90-alsa-restore.rules Elimar Riesebieter
2013-05-30 13:28 ` Elimar Riesebieter
2013-05-30 13:41   ` Elimar Riesebieter
2013-05-30 13:55 ` Jaroslav Kysela
2013-05-30 15:06   ` Elimar Riesebieter
2013-05-30 18:44     ` Jaroslav Kysela [this message]

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=51A79E1F.9070200@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=pkg-alsa-devel@lists.alioth.debian.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