Slackware 14.0slackware-14.0

Wed Sep 26 01:10:42 UTC 2012
Slackware 14.0 x86_64 stable is released!

We're perfectionists here at Slackware, so this release has been a long
time a-brewing.  But we think you'll agree that it was worth the wait.
Slackware 14.0 combines modern components, ease of use, and flexible
configuration... our "KISS" philosophy demands it.

The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a
dual-sided
32-bit/64-bit x86/x86_64 DVD.  Please consider supporting the Slackware
project by picking up a copy from store.slackware.com.  We're taking
pre-orders now, and offer a discount if you sign up for a subscription.

Thanks to everyone who helped make this happen.  The Slackware team, the
upstream developers, and (of course) the awesome Slackware user
community.

Have fun!  :-)

1 files changed, 0 insertions, 25 deletions

diff --git a/source/xap/audacious-plugins/audacious-plugins.alsa.noise.is.not.helpful.diff b/source/xap/audacious-plugins/audacious-plugins.alsa.noise.is.not.helpful.diff
deleted file mode 100644
index e904ab8d9..000000000
--- a/source/xap/audacious-plugins/audacious-plugins.alsa.noise.is.not.helpful.diff
+++ /dev/null
@@ -1,25 +0,0 @@
---- ./src/alsa/alsa.c.orig	2011-02-22 11:29:46.000000000 -0600
-+++ ./src/alsa/alsa.c	2011-03-11 15:02:53.340999637 -0600
-@@ -207,10 +207,20 @@
-             static gboolean warned = FALSE;
-             if (! warned)
-             {
--                fprintf (stderr, "\n** WARNING **\nAudacious has detected that "
-+                /* fprintf (stderr, "\n** WARNING **\nAudacious has detected that "
-                  "your ALSA device has a broken timer.  A workaround\nis being "
-                  "used to prevent CPU overload.  Please report this problem to "
--                 "your\nLinux distributor or to the ALSA developers.\n\n");
-+                 "your\nLinux distributor or to the ALSA developers.\n\n"); */
-+                  /* ^^^ COMMENTED OUT ^^^ */
-+
-+                /* I'm glad there is a workaround for this, and the reports
-+                   are that it works, so spamming the console about it seems
-+                   a little bit extreme.  It's not an issue to be solved here
-+                   by Slackware, and I would be surprised if the ALSA
-+                   developers did not know by now, given this warning.
-+                   FWIW, this seems a strange method of communicating with the
-+                   ALSA developers.  Did they report the bug to them? */
-+
-                 warned = TRUE;
-             }
-