[Lunar-commits] <moonbase> wildmidi: moved from zbeta to audio
Duncan Gibson
engelsman at lunar-linux.org
Sat Aug 1 02:22:53 CEST 2009
commit 5f6cc428d84a7dfd8dc14cdab4466f13fec6d348
Author: Duncan Gibson <engelsman at lunar-linux.org>
Date: Sat Aug 1 02:22:53 2009 +0200
wildmidi: moved from zbeta to audio
---
audio/wildmidi/BUILD | 13 +++++++++++++
audio/wildmidi/DETAILS | 44 ++++++++++++++++++++++++++++++++++++++++++++
zbeta/wildmidi/BUILD | 13 -------------
zbeta/wildmidi/DETAILS | 44 --------------------------------------------
4 files changed, 57 insertions(+), 57 deletions(-)
diff --git a/audio/wildmidi/BUILD b/audio/wildmidi/BUILD
new file mode 100644
index 0000000..7f0919f
--- /dev/null
+++ b/audio/wildmidi/BUILD
@@ -0,0 +1,13 @@
+(
+
+ # Patches from http://koji.fedoraproject.org/koji/packageinfo?packageID=4841
+ patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-opt.patch 1 &&
+ patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-cfg-abs-path.patch 1 &&
+ patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-pulseaudio.patch 1 &&
+ patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-bigendian.patch 1 &&
+
+ autoreconf -fi &&
+ OPTS+=" --disable-static --disable-werror --without-arch" &&
+ default_build
+
+) > $C_FIFO 2>&1
diff --git a/audio/wildmidi/DETAILS b/audio/wildmidi/DETAILS
new file mode 100644
index 0000000..be4d8f6
--- /dev/null
+++ b/audio/wildmidi/DETAILS
@@ -0,0 +1,44 @@
+ MODULE=wildmidi
+ VERSION=0.2.2
+ SOURCE=$MODULE-$VERSION.tar.gz
+ SOURCE_URL=$SFORGE_URL/$MODULE
+ SOURCE_VFY=sha1:fad33365f8aaba3afdca6bb68bc48056425176a3
+ WEB_SITE=http://wildmidi.sourceforge.net/
+ ENTERED=20090721
+ UPDATED=20090721
+ SHORT="a simple software midi player"
+
+cat << EOF
+WildMIDI is a simple software midi player which has a core softsynth
+library that can be use with other applications.
+
+WildMIDI was originally conceived in December 2001 as an experiment to
+see if MIDI files could be played using the same samples as existing
+software but with much less overhead. Coming into existence as a
+command-line player in 2002 the first versions were so successful in
+reducing the overhead that developers from Quakeforge suggested that
+WildMIDI could be turned into a library. 2003 saw the first
+implementations of the WildMIDI library, with Quakeforge being used as
+the test application. The 1st official release of WildMIDI occured in
+2004 with a couple of bug fixes following shortly after.
+
+The WildMIDI library uses Gravis Ultrasound patch files to convert MIDI
+files into audio which is then passed back to the calling application
+for further processing or output. The API of the library is designed so
+that it is easy to include WildMIDI into applications that wish to
+include MIDI file playback. With multiple MIDI file support you can
+develop applications to mix several midi files together at the same
+time, and with the next release you will be able to use a different
+patch set for each MIDI file.
+
+Currently there is a small command-line player that accompanies the
+library which gives just one example of the use of the WildMIDI
+library. The next release will also contain a "self-contained" player
+which will play midi files without the extra overhead that occurs with
+the library. This is achieved by having a core source that is shared
+between the library and "self-contained" player.
+
+The future of the project will not end with the library, but with the
+library the door is open to possibilities including a software MIDI
+device, or a graphical MIDI sequencer.
+EOF
diff --git a/zbeta/wildmidi/BUILD b/zbeta/wildmidi/BUILD
deleted file mode 100644
index 7f0919f..0000000
--- a/zbeta/wildmidi/BUILD
+++ /dev/null
@@ -1,13 +0,0 @@
-(
-
- # Patches from http://koji.fedoraproject.org/koji/packageinfo?packageID=4841
- patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-opt.patch 1 &&
- patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-cfg-abs-path.patch 1 &&
- patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-pulseaudio.patch 1 &&
- patch_it $SCRIPT_DIRECTORY/wildmidi-0.2.2-bigendian.patch 1 &&
-
- autoreconf -fi &&
- OPTS+=" --disable-static --disable-werror --without-arch" &&
- default_build
-
-) > $C_FIFO 2>&1
diff --git a/zbeta/wildmidi/DETAILS b/zbeta/wildmidi/DETAILS
deleted file mode 100644
index be4d8f6..0000000
--- a/zbeta/wildmidi/DETAILS
+++ /dev/null
@@ -1,44 +0,0 @@
- MODULE=wildmidi
- VERSION=0.2.2
- SOURCE=$MODULE-$VERSION.tar.gz
- SOURCE_URL=$SFORGE_URL/$MODULE
- SOURCE_VFY=sha1:fad33365f8aaba3afdca6bb68bc48056425176a3
- WEB_SITE=http://wildmidi.sourceforge.net/
- ENTERED=20090721
- UPDATED=20090721
- SHORT="a simple software midi player"
-
-cat << EOF
-WildMIDI is a simple software midi player which has a core softsynth
-library that can be use with other applications.
-
-WildMIDI was originally conceived in December 2001 as an experiment to
-see if MIDI files could be played using the same samples as existing
-software but with much less overhead. Coming into existence as a
-command-line player in 2002 the first versions were so successful in
-reducing the overhead that developers from Quakeforge suggested that
-WildMIDI could be turned into a library. 2003 saw the first
-implementations of the WildMIDI library, with Quakeforge being used as
-the test application. The 1st official release of WildMIDI occured in
-2004 with a couple of bug fixes following shortly after.
-
-The WildMIDI library uses Gravis Ultrasound patch files to convert MIDI
-files into audio which is then passed back to the calling application
-for further processing or output. The API of the library is designed so
-that it is easy to include WildMIDI into applications that wish to
-include MIDI file playback. With multiple MIDI file support you can
-develop applications to mix several midi files together at the same
-time, and with the next release you will be able to use a different
-patch set for each MIDI file.
-
-Currently there is a small command-line player that accompanies the
-library which gives just one example of the use of the WildMIDI
-library. The next release will also contain a "self-contained" player
-which will play midi files without the extra overhead that occurs with
-the library. This is achieved by having a core source that is shared
-between the library and "self-contained" player.
-
-The future of the project will not end with the library, but with the
-library the door is open to possibilities including a software MIDI
-device, or a graphical MIDI sequencer.
-EOF
More information about the Lunar-commits
mailing list