The source!
The easiest way of getting the source is via anonymous svn. Since the svn repository is divided into several smaller projects, we've created a script that handles the checkout for you. To use this, open up a command line, and type:
You can download and view the script here: checkout-from-svn.
It's also possible to checkout the code using normal svn commands. The repository root is
svn://plan99.net/ for anonymous svn and svn+ssh://username@plan99.net/autopackage for developers.
The repository can also be browsed on the Autopackage Trac site:
Installing the SVN code
Once the modules has been checked out, cd into the newly created main directory, then run:
This script sets a few things up on your machine first. Don't worry, before doing anything at all, it will state clearly what it's going to do, and it will give you a chance to abort if you don't want to continue. It's needed as the autopackage code will assume it's "installed" on the machine, ie some paths/symlinks are present. You don't need to rerun setup after updating CVS, it uses symlinks. The unsetup script can be used to remove CVS autopackage.
su -c ./setup) if you want to
make the autopackage devel tools globally available.
So now what? You'll probably want to try building a package.
Foobar is a little program we wrote to let us easily test the system. It doesn't actually do anything useful, nor anything amusing (though patches to remedy that are welcome!) What it does have it's lots of different types of files that we can play with.
Change into the foobar directory, and run configure:
That is VERY important, it will create the .spec file from the .spec.in - now run "makepackage"
Hopefully everything will have gone smoothly, but if it hasn't, then get on the mailing list and tell us about it.
Subversion tags and branches
These are the tags to build versions from SVN. The current stable version (1.2) is the "trunk" (known as HEAD in CVS terminology), while the previous stable release, 1.0, lives in the r1-0-2 branch. All tags and branches follow the standard subversion naming convention, so main/tags/r1-0-5 will get you the 1.0.5 release of the support code.
| Version | foobar, gtkfe, main, manager | apbuild |
|---|---|---|
| 1.0.0 | r1-0-0 | RELEASE-1-9-0 |
| 1.0.1 | r1-0-1 | RELEASE-1-9-0 |
| 1.0.2 | r1-0-2 | RELEASE-1-9-0 |
| 1.0.3 | r1-0-3 | RELEASE-1-9-0 |
| 1.0.4 | r1-0-4 | RELEASE-1-9-0 |
| 1.0.5 | r1-0-5 | RELEASE-1-9-0 |
| 1.0.6 | r1-0-6 | RELEASE-1-9-0 |
| 1.0.7 | r1-0-7 | RELEASE-1-9-0 |
| 1.0.8 | r1-0-8 | RELEASE-1-9-0 |
| 1.0.9 | r1-0-9 | RELEASE-1-9-0 |
| 1.0.10 | r1-0-10 | RELEASE-1-9-0 |
| 1.2 | r1-2 | October 18, 2006 |
| 1.2.1 | r1-2-1 | RELEASE-2-0-2 |
| 1.2.2 | r1-2-2 | RELEASE-2-0-3 |
| 1.2.4 | r1-2-4 | r2-0-5 |
Build Wrapper Script
There is a wrapper script that will build multiple packages from the cvs modules that are available.
In order to build the autopackage support code archive, autopackage-gtk front end, and foobar packages all at the same time, then change into the main/release directory, and run autopackage-build:
The build script will generate packages and place them into the main/release/<autopackage-version>/ directory with the autopackage-version being the current version of autopackage cvs. The build script can accept other arguments to build other packages.