Previous: Releases, Up: Obtaining Muse


3.2 Latest unreleased development changes

Choose the development version if you want to live on the bleeding edge of Muse development or try out new features before release.

The Arch revision control system allows you to retrieve previous versions and select specific features and bug fixes. If you would like to contribute to Muse development, it is highly recommended that you use Arch, but this is not a requirement.

If you are new to Arch, you might find this tutorial helpful: http://mwolson.org/projects/ArchTutorial.html.

Downloading the Muse module with Arch and staying up-to-date involves the following steps.

  1. Install arch
  2. Register the archive.
              tla register-archive -f http://mwolson.org/archives/2006
         

    You might ask why there is a mention of the year “2006” in the name of the archive. This year is not very significant—it only means that I created this archive in 2006. I used to create a new archive every year, but this was a hassle for people who were trying to track development of Muse, so I have stopped doing it.

  3. Download the Muse package.
              # Download Muse into the muse directory.
              tla get mwolson@gnu.org--2006/muse--main--1.0 muse
         
  4. List upstream changes that are missing from your local copy. Do this whenever you want to see whether new changes have been committed to Muse.
              # Change to the source directory you are interested in.
              cd muse/
              
              # Display the summary of changes
              tla missing --summary
         

  5. Update to the latest version by replaying missing changes.
              cd muse
              tla update
         

There are other ways to interact with the Muse archive.

The latest development snapshot will be kept up-to-date since it is updated at the same time as the Arch repository.