update date, and full repo size (its ~600mb larger)
as pointed out by arand, the cp magic has to happen in update = not checkout =
|Deletions are marked like this.||Additions are marked like this.|
|Line 68:||Line 68:|
|checkout = svn co svn+ssh://svn.debian.org/svn/pkg-games/mrconfig games-mrconfig ; cp ~/src/packages/games-mrconfig/.mrconfig ~/src/packages/games/.mrconfig||checkout = svn co svn+ssh://svn.debian.org/svn/pkg-games/mrconfig games-mrconfig
update = svn up ; cp ~/src/packages/games-mrconfig/.mrconfig ~/src/packages/games/.mrconfig
The Debian Games Team currently uses either git or svn to help in maintaining packages. This page will help you get started in using either git or svn repositories.
Most of the packages are independent from each other. In svn, a [trunk,tags,branches}/<package> scheme is used with only the debian directory stored. The .orig.tar.gz files in such a case are stored in /home/groups/pkg-games/htdocs/tarballs in the alioth servers. They can be accessed online at http://pkg-games.alioth.debian.org/tarballs. In git, each package has it's own repository. The contents of the orig tarball are stored directly within each package's repository, inside the 'upstream' branch. The pristine-tar program can be used to regenerate an orig tarball from the upstream branch.
The first thing to do is get an account on alioth.debian.org. Visit the following link.
The next step is to join the team. Visit the Alioth page for the team and click on "request to join".
Next, you will need an ssh key for each computer you plan on working on packages with. If you don't have a key on a particular system, create one.
This should have created an RSA key for SSH protocol 2 by default. Upload the contents of your public keys (~/.ssh/id_rsa.pub) to your account in Alioth. To do this, copy the contents of each public key for your machines and paste them at the following link.
Next, create an SSH configuration file (~/.ssh/config) for your user profile to work with the alioth servers. Here's how to do the following in a terminal session.
$ cat >>~/.ssh/config <<EOF Host svn.debian.org User <username> Host git.debian.org User <username> Host alioth.debian.org User <username> EOF
Now you should be able to logon from each of your machines by doing the following.
$ ssh svn.debian.org $ ssh git.debian.org $ ssh alioth.debian.org
Note: There's usually a one hour delay when uploading your ssh public keys. During this delay, you can still login with your password.
The mr command can be used to checkout, update, and commit to multiple repositories. In the svn+ssh://svn.debian.org/svn/pkg-games/mrconfig, is a .mrconfig file that configures mr for all the repositories used by the games team.
New git repositories should be added to this .mrconfig file.
To use it, install the mr package, and create a ~/.mrconfig file letting mr know about the pkg-games svn repository. In this example, it will be checked out to ~/src/packages/games, but you can modify to suit. If you already have a pkg-games svn checkout, you can change the directory to point to that. Note that the last field on the 'checkout' line ('games' in this instance) should match the last field of the configuration path ('src/packages/games').
[src/packages/games] chain = true checkout = svn co svn+ssh://svn.debian.org/svn/pkg-games/packages/trunk games
Then run "mr checkout", which will checkout the svn repository into ~/src/packages/games. The checkout will be approximately 120MB.
Next set up the shared games team .mrconfig. In your ~/.mrconfig, add the following entries.
# Update the games team mrconfig [src/packages/games-mrconfig] checkout = svn co svn+ssh://svn.debian.org/svn/pkg-games/mrconfig games-mrconfig update = svn up ; cp ~/src/packages/games-mrconfig/.mrconfig ~/src/packages/games/.mrconfig
An 'svn up' will pull down two files into the new directory - a README and the .mrconfig file.
Before doing the final checkout (using mr), you need to setup a ~/.mrtrust file. This is supported in all versions of mr from 0.42, and is required for chained checkouts from 1.00 (January 2011). The contents of the file should be a series of paths (one per line) to .mrconfig files. In our case, it will be one line:
Two more "mr checkout" runs (necessary because of bug #447553) will checkout the additional git repositories, into subdirectories of ~/src/packages/games/. (As of December 2011, the full debian-games repo was approx 6.5GB).
Now you can use mr to act on all configured repositories at once.
Update all repositories:
% mr update
Get status of all checkouts:
% mr status
List all repositories that mr knows about:
% mr list
Or even commit changes in each repository:
% mr commit
If you've added a new git repository in ~/src/packages/games/<foo> and are in that directory, you can have mr automatically add it to the pkg-games .mrconfig file by running "mr register". (Don't forget to commit the file.)
- If a package you're working on is for a particular version that has not been uploaded to the archive, you need to use 'UNRELEASED' as the suite in the changelog.
- packages/ in the svn repo is for free games only. For games which should go to non-free, please use non-free/package/.
- the SVN properties of the debian/ directory should point to the location where the orig.tar.gz file(s) can be fetched.