Source repositories overview

People not or not fully experienced with Subversion are strongly recommended to read the Subversion Book and the Subversion FAQ.

Subversion clients

 * RISC OS Subversion client.
 * Windows Subversion client
 * For Linux and other Unices, a Subversion client should be included in the distribution.

SVN repositories at riscos.info
All SVN repositories at svn.riscos.info have anonymous read-only access. Write-access needs an account and password.

Unless otherwise noted:
 * all svn.riscos.info SVN repositories have the RISC OS filetypes of their files encoded using the ",xyz" hex suffix method. This means that, if using the RISC OS subversion client, the  system variable must be set. See the svn !Help file for more details.
 * the repositories follow the layout conventions suggested in the svn book. (That is, branches are kept in  and tags in  .)

You can view the contents of all available SVN repositories using the WebSVN interface.

Commit notification mailing list
Many of the projects are configured to send an email when changes (commits) are made to the repositories. To receive these emails, subscribe to the riscos-commits mailing list.

SVN Repository List
The following SVN repositories are available:

GCCSDK & Autobuilder

 * GCCSDK and Autobuilder sources are stored in one repository gccsdk. To check out the 'trunk', use:
 * The gccsdk repository has its trunk at, branches at   and tags at   as subdirectories of the gccsdk repository.
 * The autobuilder code is located at  and does not have any branches nor tags so far.
 * Note that the code at  is not stable and is currently used for future GCCSDK GCC 4.x developments (based on GCC 4.7.x).  If you want the currently latest and stable GCCSDK code branch (which is  ), instead use:
 * The following are the most important tags used:
 * release_4_1_2_v2 : tree snapshot for the GCCSDK GCC 4.1.2 Release 2 release.
 * release_4_1_2_v1 : tree snapshot for the GCCSDK GCC 4.1.2 Release 1 release.
 * release_4_1_1_v2 : tree snapshot for the GCCSDK GCC 4.1.1 Release 2 release.
 * release_3_4_6_v3 : tree snapshot for the GCCSDK GCC 3.4.6 Release 3 release.
 * release_3_4_6_v2 : tree snapshot for the GCCSDK GCC 3.4.6 Release 2 release.
 * release_3_4_6_v1 : tree snapshot for the GCCSDK GCC 3.4.6 Release 1 release.
 * release_3_4_5_v1 : tree snapshot for the GCCSDK GCC 3.4.5 Release 1 release.
 * release_3_4_4_v3 : tree snapshot for the GCCSDK GCC 3.4.4 Release 3 release.
 * release_3_4_4_v2 : tree snapshot for the GCCSDK GCC 3.4.4 Release 2 release.
 * release_3_4_4 : tree snapshot for the GCCSDK GCC 3.4.4 Release 1 release.
 * release_3_4_1 : tree snapshot for the GCCSDK GCC 3.4.1 Release 1 release.
 * release_3_3_3_pre2 : tree snapshot for the GCCSDK GCC 3.3.3 pre-release 2 release.
 * release_2_95_4_v3 : tree snapshot for the GCCSDK GCC 2.95.4 Release 3 release.
 * The following are the most important branches used:
 * release_4_1_2 : stable branch containing minor fixes and enhancements for the GCCSDK GCC 4.1.2 releases.
 * release_4_1_1 : closed branch, this was the stable branch for the GCCSDK GCC 4.1.1 releases.
 * release_3_4_6 : closed branch, this was the stable branch for the GCCSDK GCC 3.4.6 releases.
 * release_3_4_4_v2_stable : closed branch, this was the stable branch for the GCCSDK GCC 3.4.4 releases.
 * release_3_3 : closed branch, this was the development branch for all GCCSDK 3.3 based work.
 * release_2_95 : closed branch, this was the development branch for all GCCSDK 2.95 based work.
 * More info on these GCCSDK releases can be found at the GCCSDK releases page.
 * release_2_95 : closed branch, this was the development branch for all GCCSDK 2.95 based work.
 * More info on these GCCSDK releases can be found at the GCCSDK releases page.

QEMU

 * RISC OS and GCCSDK specific changes to the QEMU project are stored in the repository.


 * Revision 2 contains a snapshot of QEMU CVS repository made on 2006-03-21 01:00:00 CET. The trunk will be from time to time updated with snapshots taken from the QEMU CVS repository.  The RISC OS and GCCSDK specific changes will be made in the branch riscos.