From: Takashi Iwai <tiwai@suse.de>
To: Thierry Vignaud <tvignaud@mandrakesoft.com>
Cc: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Lars Heineken <Lars.Heineken@gmx.de>,
alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] add support for mandrake in alsaconf
Date: Tue, 25 Nov 2003 13:16:18 +0100 [thread overview]
Message-ID: <s5had6k1w4t.wl@alsa2.suse.de> (raw)
In-Reply-To: <m2n0aly09n.fsf@vador.mandrakesoft.com>
At Mon, 24 Nov 2003 20:33:40 +0000,
Thierry Vignaud wrote:
>
> Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU> writes:
>
> > > > Options:
> > > > a) define 'distribution="redhat"' for the mandrake detection
> > > > code _if_ the oss options erasure for redhat works fine under
> > > > mandrake (mandrake users should test this).
> > > > b) add another handler for mandrake's modules.conf oss options
> > > > (should be written taking into account whatever mandrake uses to
> > > > configure sound so that the proper strings are removed from
> > > > modules.conf).
> > >
> > > so why not doing such as threat all distros that provide
> > > /etc/redhat-release the same way. i don't think there's any
> > > distro out that provide /etc/redhat-release for compatibility that
> > > would like to have users loose their module configuration:
> >
> > With the patch I supplied no distros that user /etc/redhat-release
> > will lose their configuration (I hope, at least not due to the bug I
> > introduced a long time ago which is fixed by the patch). Distros
> > that are not RedHat or Fedora will execute the SuSE code path.
> >
> > Your patch is fine, I would say. But it has an assumption I don't
> > quite like. I wrote "remove_sndconfig_block" (basing it on
> > "remove_y2_block") by looking at all the strings that the sndconfig
> > utility was adding to modules.conf (sndconfig was the way RedHat was
> > doing sound configuration quite a while ago, I think this has
> > changed).
>
> as for mandrake, we do not rely on sndconfig (though we still provide
> it for isa pnp sound card owners)
>
> drakx (the installer) and draksound (the standalone soundconfig tool)
> only write "sound-slot-X" aliases and "above XXX snd-pcm-oss" lines
> for oss compatibility (if $module =~ /^snd-/) in /etc/modules.conf
then remove_y2_block() would be enough.
i'll take Thierry's first patch. it will be in pre3 release.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-11-25 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 23:40 fedora core alsaconf patch Fernando Pablo Lopez-Lezcano
2003-11-22 10:18 ` Lars Heineken
2003-11-24 2:39 ` Fernando Pablo Lopez-Lezcano
2003-11-24 14:59 ` [PATCH] add support for mandrake in alsaconf Thierry Vignaud
2003-11-24 15:15 ` Takashi Iwai
2003-11-24 18:58 ` Fernando Pablo Lopez-Lezcano
2003-11-24 19:42 ` Thierry Vignaud
2003-11-24 20:03 ` Fernando Pablo Lopez-Lezcano
2003-11-24 20:33 ` Thierry Vignaud
2003-11-25 12:16 ` Takashi Iwai [this message]
2003-11-24 11:45 ` fedora core alsaconf patch 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=s5had6k1w4t.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Lars.Heineken@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nando@ccrma.Stanford.EDU \
--cc=tvignaud@mandrakesoft.com \
/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.