- THE BAD
-
- --- "That an accusation?"
-
-No perfectly groomed moustache or any amount of fine clothing is going to
-cover up the truth - these plug-ins are Bad with a capital B.
-They look fine on the outside, and might even appear to get the job done, but
-at the end of the day they're a black sheep. Without a golden-haired angel
-to watch over them, they'll probably land in an unmarked grave at the final
-showdown.
-
-Don't bug us about their quality - exercise your Free Software rights,
-patch up the offender and send us the patch on the fastest steed you can
-steal from the Confederates. Because you see, in this world, there's two
-kinds of people, my friend: those with loaded guns and those who dig.
-You dig.
-
-The Lowdown
------------
-
- --- "I've never seen so many plug-ins wasted so badly."
-
-GStreamer Plug-ins has grown so big that it's hard to separate the wheat from
-the chaff. Also, distributors have brought up issues about the legal status
-of some of the plug-ins we ship. To remedy this, we've divided the previous
-set of available plug-ins into four modules:
-
-- gst-plugins-base: a small and fixed set of plug-ins, covering a wide range
- of possible types of elements; these are continuously kept up-to-date
- with any core changes during the development series.
-
- - We believe distributors can safely ship these plug-ins.
- - People writing elements should base their code on these elements.
- - These elements come with examples, documentation, and regression tests.
-
-- gst-plugins-good: a set of plug-ins that we consider to have good quality
- code, correct functionality, our preferred license (LGPL for the plug-in
- code, LGPL or LGPL-compatible for the supporting library).
-
- - We believe distributors can safely ship these plug-ins.
- - People writing elements should base their code on these elements.
-
-- gst-plugins-ugly: a set of plug-ins that have good quality and correct
- functionality, but distributing them might pose problems. The license
- on either the plug-ins or the supporting libraries might not be how we'd
- like. The code might be widely known to present patent problems.
-
- - Distributors should check if they want/can ship these plug-ins.
- - People writing elements should base their code on these elements.
-
-- gst-plugins-bad: a set of plug-ins that aren't up to par compared to the
- rest. They might be close to being good quality, but they're missing
- something - be it a good code review, some documentation, a set of tests,
- a real live maintainer, or some actual wide use.
- If the blanks are filled in they might be upgraded to become part of
- either gst-plugins-good or gst-plugins-ugly, depending on the other factors.
-
- - If the plug-ins break, you can't complain - instead, you can fix the
- problem and send us a patch, or bribe someone into fixing them for you.
- - New contributors can start here for things to work on.
-
-INSTALLING FROM PACKAGES
-------------------------
-You should always prefer installing from packages first. GStreamer is
-well-maintained for a number of distributions, including Fedora, Debian,
-Ubuntu, Mandrake, Gentoo, ...
-
-Only in cases where you:
-- want to hack on GStreamer
-- want to verify that a bug has been fixed
-- do not have a sane distribution
-should you choose to build from source tarballs or CVS.
-
-Find more information about the various packages at
-http://gstreamer.freedesktop.org/download/
-
-COMPILING FROM SOURCE TARBALLS
-------------------------------
-- again, make sure that you really need to install from source !
- If GStreamer is one of your first projects ever that you build from source,
- consider taking on an easier project.
-
-- check output of ./configure --help to see if any options apply to you
-- run
- ./configure
- make
-
- to build GStreamer.
-- if you want to install it (not required), run
- make install
-- You should create a registry for things to work.
- If you ran make install in the previous step, run
- gst-register
- as root.
-
- If you didn't install, run
- tools/gst-register
- as a normal user.
-
-- try out a simple test:
- gst-launch fakesrc num_buffers=5 ! fakesink
- (If you didn't install GStreamer, again prefix gst-launch with tools/)
-
- If it outputs a bunch of messages from fakesrc and fakesink, everything is
- ok.
-
-- After this, you're ready to install gst-plugins, which will provide the
- functionality you're probably looking for by now, so go on and read
- that README.
-
-COMPILING FROM CVS
-------------------
-When building from CVS sources, you will need to run autogen.sh to generate
-the build system files.
-
-You will need a set of additional tools typical for building from CVS,
-including:
-- autoconf
-- automake
-- libtool
-
-autogen.sh will check for recent enough versions and complain if you don't have
-them. You can also specify specific versions of automake and autoconf with
---with-automake and --with-autoconf
-
-Check autogen.sh options by running autogen.sh --help
-
-autogen.sh can pass on arguments to configure - you just need to separate them
-from autogen.sh with -- between the two.
-prefix has been added to autogen.sh but will be passed on to configure because
-some build scripts like that.
-
-When you have done this once, you can use autoregen.sh to re-autogen with
-the last passed options as a handy shortcut. Use it.
-
-After the autogen.sh stage, you can follow the directions listed in
-"COMPILING FROM SOURCE"
-
-You can also run your whole cvs stack uninstalled. The script in
-the gstreamer module /docs/faq/gst-uninstalled) is helpful in setting
-up your environment for this.
-
-PLUG-IN DEPENDENCIES AND LICENSES
----------------------------------
-GStreamer is developed under the terms of the LGPL (see LICENSE file for
-details). Some of our plug-ins however rely on libraries which are available
-under other licenses. This means that if you are using an application which
-has a non-GPL compatible license (for instance a closed-source application)
-with GStreamer, you have to make sure not to use GPL-linked plug-ins.
-When using GPL-linked plug-ins, GStreamer is for all practical reasons
-under the GPL itself.
-
-HISTORY
--------
-The fundamental design comes from the video pipeline at Oregon Graduate
-Institute, as well as some ideas from DirectMedia. It's based on plug-ins that
-will provide the various codec and other functionality. The interface
-hopefully is generic enough for various companies (ahem, Apple) to release
-binary codecs for Linux, until such time as they get a clue and release the
-source.
+
+This module contains a set of plug-ins that have good quality and correct
+functionality, but distributing them might pose problems. The license
+on either the plug-ins or the supporting libraries might not be how we'd
+like. The code might be widely known to present patent problems.
+Distributors should check if they want/can ship these plug-ins.
+
+
+Other modules containing plug-ins are:
+
+
+gst-plugins-base
+contains a basic set of well-supported plug-ins
+gst-plugins-good
+contains a set of well-supported plug-ins under our preferred license
+gst-plugins-bad
+contains a set of less supported plug-ins that haven't passed the
+ rigorous quality testing we expect
+
+
+
+
+Features of this release
+
+ * Parallel installability with 0.8.x series
+ * Threadsafe design and API
+ * lame, rmdemux, iec958 fixes
+
+Bugs fixed in this release
+
+
+Download
+
+You can find source releases of gst-plugins-ugly in the download directory:
+http://gstreamer.freedesktop.org/src/gst-plugins-ugly/
+
+GStreamer Homepage
+
+More details can be found on the project's website:
+http://gstreamer.freedesktop.org/
+
+Support and Bugs
+
+We use GNOME's bugzilla for bug reports and feature requests:
+http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer
+
+Developers
+
+CVS is hosted on cvs.freedesktop.org.
+All code is in CVS and can be checked out from there.
+Interested developers of the core library, plug-ins, and applications should
+subscribe to the gstreamer-devel list. If there is sufficient interest we
+will create more lists as necessary.
+
+
+Applications
+
+Contributors to this release
+
+ * Flavio Oliveira
+ * Michael Smith
+ * Stefan Kost
+ * Thomas Vander Stichele
+ * Wim Taymans
+
\ No newline at end of file