Development > MusicBrainz Projects
The list of modules currently under source control
This is the list of modules currently under source control. Each of these modules has its own set of release numbers / tags which you can use if desired.
- The libdiscid library for creating MusicBrainz DiscIDs, based on libmusicbrainz-2, but written in C.
- This project contains the sources for building the MusicBrainz Client Library (or libmusicbrainz), which allows the end user to request data from the RDF web service and look up TRM IDs from WAV audio data.
- This project contains the sources for building TunePimp (or libtunepimp), which provides a basic framework for tagger applications. Using this library, it is easy to write a complete tagging application -- only a UI layer needs to be added. This library handles all the tricky details of reading and writing metadata tags, looking up PUIDs from various audio formats, and matching the information extracted from the local digital audio files with the fingerprint information stored in MusicBrainz. Also includes Perl bindings.
- mb_server (Classic)
- The "classic" MusicBrainz Server (pre-May 2011). Most of this code is written in Perl and is designed to run inside the Apache web server, using mod_perl with the Mason web framework. Further development on this version of MusicBrainz has been stopped.
- mb_server (Current / NGS)
- The current version of MusicBrainz Server (post-May 2011). Most of this code is written in Perl and is designed to run inside the Apache web server, using mod_perl with the Catalyst framework and Template Toolkit.
- Source code for the legacy windows-only tagger application (see MusicBrainz Tagger). Further development on this project has been stopped, it has been replaced with MusicBrainz Picard. Borland C++ builder 6.0 is required to build this project.
- Command-line based tagger, uses the lucene index.
- Reference implementation bindings for the new web service. (see PythonMusicBrainz2).
- Text-search solution based on Lucene. Contains 2 modules: the index builder and the web service.
Checking out a project from source control
In all cases, by doing a plain "checkout" of a module you retrieve the latest development copy (i.e. trunk), which will not necessarily be stable. If you want a stable copy, usually a numbered release, you'll need to find the correct Subversion tag corresponding to the release you want, you can then fetch it by appending the
/tags/sometagname to the repository url. For example, if you want to fetch the 2.0.2 release of libmusicbrainz you have to use this command:
svn co http://svn.musicbrainz.org/libmusicbrainz/tags/release-2-0-2 libmusicbrainz
Whereas to fetch the latest, unstable version you have to use this command:
svn co http://svn.musicbrainz.org/libmusicbrainz/trunk libmusicbrainz