Changes http://wiki.axiom-developer.org/AxiomSilverGoogle/diff --
??changed: - +Obtaining a working copy from the Google SVN repository + + The Google repository is meant to be an alternative for obtaining the AxiomSilver sources. + + *THIS REPOSITORY IS NOT MEANT TO BE USE TO COMMIT CHANGES TO AXIOM* + + * SVN requirements: + + You need a working SVN command that supports the HTTP protocol. + You can get a copy from + + http://subversion.tigris.org/ + + Here is an excellent online book on version control with Subversion + + http://svnbook.red-bean.com/ + + * read-only access: + + Check out the silver branch of Axiom source code with:: + + svn co https://svn.sourceforge.net/svnroot/axiom/trunk axiom.silver + + That command will create a directory, named axiom.silver, to + hold checked out copy of the Axiom source code. Please, feel free to + replace 'axiom.silver' with any name that suits your taste. + + If you are only interested in a particular development branch, say + build-improvement, you may say:: + + svn co https://svn.sourceforge.net/svnroot/axiom/branches/build-improvements \ + axiom.build-improvements + + * read and write access: + + You need to have a Sourceforge user id, and be registered as a developer. + + To obtain a working copy with write privilege to the sourceforge + repository you might want to append '--username=<sf-user-id>' to the + above commands, where <sf-user-id> is your sourceforge user id. + + * "Core" developers: + + Some developers might prefer to have a working copy of the "whole" + axiom repository, in that case they might want to issue:: + + svn co https://svn.sourceforge.net/svnroot/axiom axiom + + That will check out the Axiom main repository into a local + directory named axiom. It should contain the following + subdirectories:: + + branches/ + tags/ + trunk/ + + that are self-explanatory. -- forwarded from http://wiki.axiom-developer.org/[EMAIL PROTECTED]
