Skip to main content


Project description


Makes bzr/hg/git/svn checkouts in several places according to a config file.

The advantage: you’ve got one command with which you can update all your checkouts. And with which you can ask for a list of uncommitted changes. And you can rebuild your entire checkout structure on a new machine just by copying the config file (this was actually the purpose I build it for: I had to change laptops when I switched jobs…).

Warning: I only tested it on OSX and linux, so no guarantees for windows. If there are changes needed, they’ll probably be minor. So I welcome bug reports and patches.

Generic usage

What I normally do every morning when I get to work is checkoutmanager up. This grabs the latest versions of all my checkouts from the server(s). So an svn up for my subversion checkouts, a hg pull -u for mercurial and so on.

From time to time, I’ll do a checkoutmanager st to show if I’ve got some uncommitted files lying around somewhere. Very handy if you’ve worked in several directories throughout the day: it prevents you from forgetting to check in that one bugfix for a whole week.

A new project means I add a single line to my config file and run checkoutmanager co.

Checkoutmanager allows you to spread your checkouts over multiple directories. It cannot mix version control systems per directory, however. As an example, I’ve got a ~/buildout/ directory with my big svn website projects checked out there. And a directory with my svn work python libraries. And a ~/hg/ dir with my mercurial projects. And I’ve made checkouts of several config directories in my home dir, such as ~/.emacs.d, ~/.subversion and so on. Works just fine.


Available commands:


Print whether checkouts are present or missing


Grab latest version from the server.


Print status of files in the checkouts


Grab missing checkouts from the server


Print directories that are missing from the config file

Output directory naming

If you don’t specify an output directory name for your checkout url, it just takes the last part. One exception: subversion. It is intelligent there:

  • https://xxx/yyy/product/trunk becomes “product” instead of “trunk”.

  • https://xxx/yyy/product/branches/experiment becomes “product_experiment” instead of “experiment”

If you want something else, just specify a directory name (separated by a space) in the configuration file.

Config file

Sample configuration file:

# Sample config file.  Different sections per base location and version
# control system.  Splitting everything all over the place in multiple
# directories is fine.

# Buildout recipes I work on.
vcs = svn
basedir = ~/svn/recipes
checkouts =
    svn://svn/another/trunk differentname

# Folders that end up as dotted configfolders in the root.
vcs = bzr
basedir = ~
checkouts =
    lp:emacsconfig/trunk .emacs.d
    sftp://somwhere/subversion/trunk .subversion


  • Wait for windows bug reports and fix a couple of small things.

  • Wait for feedback so that I can improve the documentation.


Created by Reinout van Rees.

Changelog of vanrees.checkoutmanager

1.0 (2010-08-01)

  • Small fixes. It works great in practice.

  • Moved from bzr to hg and made it public on

  • Big documentation update as I’m going to release it.

0.1 (2010-05-07)

  • First reasonably working version.

  • Initial library skeleton created by thaskel.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

checkoutmanager-1.0.tar.gz (7.4 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page