Initial revision

AUTHORS

@@ -0,0 +1,5 @@
+Jorn Baayen <[email protected]>
+Marco Pesenti Gritti <[email protected]>
+Bastien Nocera <[email protected]>
+Seth Nickell <[email protected]>
+Olivier Martin <[email protected]>

ChangeLog

@@ -0,0 +1,3 @@
+2002-06-01  Jorn Baayen  <[email protected]>
+
+	* new skels

HACKING

@@ -0,0 +1,18 @@
+In order to keep the code nice and clean we have a few requirements you'll
+need to stick to in order to get your patch accepted:
+
+- use 8-space tabs for indentation
+- curly brackets are on a new line
+- please compare with NULL or FALSE isntead of using "!"
+- if statements are written like this: "if (this != that)"
+- g_list_next/previous is preferred to list->next or list->previous
+- every function should have a prototype
+
+  Comment blocks are written like this:
+
+/**
+ * bla_bla_cb: This is an example comment block
+ */
+
+Do NOT commit to this module without permission from me (jorn on IRC,
+[email protected] email addy)

INSTALL

@@ -0,0 +1,29 @@
+Prerequisites
+=============
+
+Rhythmbox requires the following packages:
+
+ - A working GNOME 2 platform (more specifically, you need glib-2.0, gtk+-2.0,
+   gnome-vfs-2.0, libgnome-2.0, gconf-2.0 and libglade-2.0.)
+   For more information, see:
+
+    http://www.gnome.org/
+
+ - The MonkeyMedia multimedia library, available from:
+
+    http://nl.linux.org/~jorn/monkey-media.html
+
+Simple install procedure
+========================
+
+  % gzip -cd rhythmbox-0.3.tar.gz | tar xvf -    # unpack the sources
+  % cd rhythmbox-0.3                             # change to the directory
+  % ./configure                                  # run the 'configure' script
+  % make                                         # build Rhythmbox
+  [ Become root if necessary ]
+  % make install                                 # install Rhythmbox
+
+The Details
+===========
+
+More detailed installation instructions can be found in INSTALL.GNU.

INSTALL.GNU

@@ -0,0 +1,182 @@
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, a file
+`config.cache' that saves the results of its tests to speed up
+reconfiguring, and a file `config.log' containing compiler output
+(useful mainly for debugging `configure').
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If at some point `config.cache'
+contains results you don't want to keep, you may remove or edit it.
+
+   The file `configure.in' is used to create `configure' by a program
+called `autoconf'.  You only need `configure.in' if you want to change
+it or regenerate `configure' using a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  You can give `configure'
+initial values for variables by setting them in the environment.  Using
+a Bourne-compatible shell, you can do that on the command line like
+this:
+     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+
+Or on systems that have the `env' program, you can do it like this:
+     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not supports the `VPATH'
+variable, you have to compile the package for one architecture at a time
+in the source code directory.  After you have installed the package for
+one architecture, use `make distclean' before reconfiguring for another
+architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on.  Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+     CPU-COMPANY-SYSTEM
+
+See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+
+   If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Operation Controls
+==================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--cache-file=FILE'
+     Use and save the results of the tests in FILE instead of
+     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
+     debugging `configure'.
+
+`--help'
+     Print a summary of the options to `configure', and exit.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--version'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`configure' also accepts some other, not widely useful, options.

MAINTAINERS

@@ -0,0 +1 @@
+Jorn Baayen <[email protected]>

Makefile.am

@@ -0,0 +1,8 @@
+SUBDIRS = lib tests library shell data
+
+EXTRA_DIST = 			\
+	autogen.sh		\
+	intltool-merge.in	\
+	intltool-update.in	\
+	intltool-extract.in	\
+	INSTALL.GNU

NEWS

@@ -0,0 +1,39 @@
+Overview of Changes in Rhythmbox 0.3
+====================================
+
+* total rewrite [Jorn Baayen]
+
+Overview of Changes in Rhythmbox 0.2.2
+======================================
+
+* MonkeyMedia 0.5 compatibility [Jorn Baayen]
+
+Overview of Changes in Rhythmbox 0.2.1
+======================================
+
+* Build fixes [Bastien Nocera]
+
+Overview of Changes in Rhythmbox 0.2
+====================================
+
+* Bugfixes [Seth Nickell, Jorn Baayen]
+* LCD widget [Jorn Baayen]
+* UI improvements [Seth Nickell]
+* Playlist columns configurable [Jorn Baayen]
+* Speed improvements [Seth Nickell, Jorn Baayen]
+* Searching [Seth Nickell, Jorn Baayen]
+* Smart Sorting of playlists [Jorn Baayen]
+* Shuffle/repeat [Jorn Baayen]
+* Splashscreen [Jakub Steiner, Olivier Martin]
+* Icons registered with the Gtk stock system [Jorn Baayen]
+* Statusbar [Jorn Baayen]
+* Proper support for "Various Artist" albums [Jorn Baayen]
+* Threaded song addition [Seth Nickell]
+* CORBA interface [Jorn Baayen]
+
+..and much more!
+
+Overview of Changes in Rhythmbox 0.1
+====================================
+
+* First release! [Jorn Baayen, Marco Pesenti Gritti, Bastien Nocera]

README

@@ -0,0 +1,64 @@
+General Information
+===================
+
+This is Rhythmbox version 0.3. Rhythmbox is your one-stop multimedia
+application, supporting a music library, multiple "music groups",
+internet radio, and more.
+
+Rhythmbox is free software, licensed under the GNU GPL.
+
+The official web site is:
+  http://www.rhythmbox.org/
+
+Information about mailing lists can be found at:
+  http://lists.sourceforge.net/lists/listinfo/rhythmbox-devel
+
+Our IRC channel is #rhythmbox on GIMPnet (irc.gimp.org).
+
+Rhythmbox CVS is hosted at gnome.org, rhythmbox-new module.
+
+Installation
+============
+
+See the file 'INSTALL'
+
+How to report bugs
+==================
+
+Bugs should be reported to the GNOME bug tracking system.
+(http://bugzilla.gnome.org, product rhythmbox.) You will need to create an
+account for yourself.
+
+In the bug report please include:
+
+* Information about your system. For instance:
+
+   - MonkeyMedia version
+   - GStreamer version
+   - Available GStreamer plugins (run gst-inspect with no arguments)
+
+  And anything else you think is relevant.
+
+* How to reproduce the bug.
+
+  If you can reproduce the bug with one of the programs in tests/, that
+  will be most convenient.  Otherwise, please include a short test program
+  that exhibits the behavior.  As a last resort, you can also provide
+  a pointer to a larger piece of software that can be downloaded.
+
+* If the bug was a crash, the exact text that was printed out when the
+  crash occured, and a trace (which can be obtained by using gdb or bug-buddy).
+
+Patches
+=======
+
+Patches should also be submitted to bugzilla.gnome.org. If the patch fixes
+an existing bug, add the patch as an attachment to that bug report.
+
+Otherwise, enter a new bug report that describes the patch, and attach
+the patch to that bug report.
+
+Bug reports containing patches should include the PATCH keywoard in their
+keyword field.
+
+Patches should be in unified diff form. (The -u option to GNU diff.)

THANKS

@@ -0,0 +1,3 @@
+Christian Schaller (Uraeus), RPM spec file, .desktop file
+Jakub Steiner (jimmac), lots of cool graphics
+James Willcox (snorp), rb-image-button

acconfig.h

@@ -0,0 +1,5 @@
+#undef ENABLE_NLS
+#undef HAVE_CATGETS
+#undef HAVE_GETTEXT
+#undef GETTEXT_PACKAGE
+#undef HAVE_LC_MESSAGES

autogen.sh

@@ -0,0 +1,21 @@
+#!/bin/sh
+# Run this to generate all the initial makefiles, etc.
+
+srcdir=`dirname $0`
+test -z "$srcdir" && srcdir=.
+
+PKG_NAME="rhythmbox"
+
+(test -f $srcdir/configure.in \
+  && test -f $srcdir/ChangeLog \
+  && test -d $srcdir/shell) || {
+    echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
+    echo " top-level $PKG_NAME directory"
+    exit 1
+}
+
+which gnome-autogen.sh || {
+    echo "You need to install gnome-common from the GNOME CVS"
+    exit 1
+}
+USE_GNOME2_MACROS=1 . gnome-autogen.sh