[Pkg-alsa-devel] [Debian ALSA CVS] debian/alsa-driver/debian (alsa-base.NEWS)

David B Harris dbharris-guest@haydn.debian.org
Sun, 25 Apr 2004 23:11:08 -0600


    Date: Sunday, April 25, 2004 @ 23:11:08
  Author: dbharris-guest
    Path: /cvsroot/pkg-alsa/debian/alsa-driver/debian

Modified: alsa-base.NEWS

Rewrite alsa-base.NEWS


----------------+
 alsa-base.NEWS |   38 ++++++++++++++++++++++++++------------
 1 files changed, 26 insertions(+), 12 deletions(-)


Index: debian/alsa-driver/debian/alsa-base.NEWS
diff -u debian/alsa-driver/debian/alsa-base.NEWS:1.4 debian/alsa-driver/debian/alsa-base.NEWS:1.5
--- debian/alsa-driver/debian/alsa-base.NEWS:1.4	Wed Apr 21 03:03:53 2004
+++ debian/alsa-driver/debian/alsa-base.NEWS	Sun Apr 25 23:11:08 2004
@@ -1,21 +1,35 @@
 alsa-driver (1.0.4-2) unstable; urgency=low
 
-  * Steve Kowalik:
-    - No longer load modules in the alsa init script. Loading modules is now
-      the responsibility of the user (using something like /etc/modules), or 
-      a program such as discover or hotplug.
-    - Provide /etc/hotplug/blacklist.d/alsa-base, which blacklists every OSS
-      sound driver.
-    - Also provide an alsa-base.discover file in /usr/share/doc/alsa-base, 
-      which skips every OSS sound driver. It can not be added to the discover 
-      config file automatically, since Policy prohibits us from modifying 
-      another package's config files.
+  After Woody's release, and previous to Sarge's release, the Debian ALSA
+  packages (specifically alsa-base) took it upon themselves to help the user
+  choose which modules to load at boot-time, and then did so on their behalf
+  via an init script, /etc/init.d/alsa. With Sarge's release, viable generic
+  autoloading mechanisms such as hotplug and discover are available. In this
+  vein, alsa-base no longer handles module loading itself, and facilitates the
+  use of discover and hotplug. Briefly, the changes are:
+
+    - Modules are no longer loaded in the /etc/init.d/alsa script. Modules
+      should be loaded via standard mechanisms such as /etc/modules,
+      /etc/modprobe.d/, /etc/modutils/, discover, or hotplug.
+    - /etc/hotplug/blacklist.d/alsa-base has been created, which causes
+      hotplug to ignore OSS modules upon alsa-base's installation. It will
+      load ALSA modules instead, when it starts and that file is in place.
+    - /usr/share/doc/alsa/alsa-base.discover has been provided for the user.
+      It's a config file snippet for use with discover, which provides much
+      the same functionality as /etc/hotplug/blacklist.d/alsa-base. discover
+      doesn't provide a method for changing its configuration file in an
+      automated manner, however, so the user must manage this change manually.
+
+  If you are upgrading from Woody, you don't need to worry about any of these
+  changes, they only affect people who were using Sid and pre-release Sarge.
 
  -- Steve Kowalik <stevenk@debian.org>  Wed, 21 Apr 2004 19:00:29 +1000
 
 alsa-driver (0.9.3a-2) unstable; urgency=low
 
-  * David B Harris:
-    - Move /etc/alsa/alsa-base.conf to /etc/default/alsa (Policy 10.3.2)
+  /etc/alsa/alsa-base.conf has been moved to /etc/default/alsa, to comply with
+  Debian Policy section 10.3.2. If you are upgrading from a version of this
+  package which uses /etc/alsa/alsa-base.conf, it will be migrated for you
+  automatically.
 
  -- Steve Kowalik <stevenk@debian.org>  Thu, 22 May 2003 00:23:08 +1000