File: http://svn.ist-palcom.org/svn/palcom/doc/setup/Palcom-SVN.txt Introduction to using the PalCom Subversion (svn) Repository. 1. Subversion Introduction Subversion (a.k.a. SVN) is meant as a replacement for CVS. It has almost the same commands as CVS, but is improved in a number of ways, notably directory handling, binary files handling and offline mode. Here are some good references: - Subversion Home http://subversion.tigris.org/ - Version Control with Subversion http://svnbook.red-bean.com/en/1.0/index.html Free online "Bible" - Subversion for CVS Users http://svnbook.red-bean.com/en/1.0/apa.html Appendix of above book, with important differences explained - Subversion for CVS Users http://osdir.com/Article203.phtml Another short guide for previous CVS users - Subversion Quick Reference Card http://www.cs.put.poznan.pl/csobaniec/Papers/svn-refcard.pdf 2 page summary of commands 2. The PalCom Subversion Repository Location The repository is located in http://svn.ist-palcom.org/svn/palcom 3. SVN usernames In order to be able to commit changes to the repository, you must be a registered user. Contact to get a username. For read-only checkout of the trunk, you need not a username. 4. Command line checkout If you have installed the command line tool "svn" (see Tools below), you can check out the main trunk of the repository read only into a local directory named "palcom" as such: svn checkout http://svn.ist-palcom.org/svn/palcom/trunk palcom Only the trunk can be checked out anonymously. If you are a registered developer, you can check out with permission to commit as such: svn checkout --username http://svn.ist-palcom.org/svn/palcom/trunk palcom Checking out into a local directory named "palcom" is currently required for the build process to work. For non-registered developers, the username "anon" with password "anon" can also be used. This gives read-only rights, just like true anonymous checkout. The main use of this is from the Eclipse Subclipse plugin, that always asks for a username on palcom checkout (see Eclipse-SVN.txt). 5. WWW Access to the Repository The repository can be browsed at http://svn.ist-palcom.org/svn/palcom 6. Using SVN with Eclipse. See http://svn.ist-palcom.org/svn/palcom/doc/setup/Eclipse-SVN.txt 7. Tools - Platform independent: Eclipse: - Plugin: http://subclipse.tigris.org/ or, alternatively use: http://www.polarion.org/index.php?page=overview&project=subversive RapidSVN: - http://rapidsvn.tigris.org/ SmartSVN: - http://www.syntevo.com/smartsvn/index.jsp - Windows: - Explorer extension: http://tortoisesvn.tigris.org/ - Using Subversion On Windows: http://weblogs.asp.net/nleghari/articles/subversion.aspx - cygwin: http://www.cygwin.com/setup.exe, package "subversion" - Macintosh: - Finder extension: http://scplugin.tigris.org/ http://www.eyefodder.com/blog/2007/06/subversion_and_finder_integrat.shtml - Subversion With Mac OS X Tutorial http://www.rubyrobot.org/tutorial/subversion-with-mac-os-x - Subversion on Mac OSX: http://forevergeek.com/geek_resources/subversion_on_mac_osx.php - How to Install Subversion on Mac OS X http://www.wikihow.com/Install-Subversion-on-Mac-OS-X - svnX: http://www.lachoseinteractive.net/en/community/subversion/svnx - Xcode: http://developer.apple.com/tools/subversionxcode.html - Linux: - Nautilus GNOME extension: http://naughtysvn.tigris.org/ - A subversion client for KDE http://kdesvn.alwins-world.de/ 8. Content of Repository The following briefly describes the content of the Repository. 8.1 Overview The basic structure is simple: palcom/ bin/ doc/ lib/ developer/ application-layer/ middleware-managers/ frameworks/ util/ runtime-environment/ engine/ core/ rte-util/ tools/ dev-bin/ dev-lib/ See palcom/doc/setup/figures/projects.png for a graphical overview, and see PalCom Open Source Doc (Working Note 117) for a detailed walk-through of the Repository. 8.2 Explanation A traditional top level structure has been adopted, resembling the most well-known top level structure for open-source projects. palcom/bin and palcom/lib: contains scripts and binary files, which allows use of a fresh check-out "out-of-the-box" (without installing Eclipse etc.), but still with full access to the sources (unlike traditional binary distributions). You simply add "palcom/bin" to your PATH and you will have access to all the "pal-*" scripts, that will execute the executable files appropriate for your platform from subdirectories of "palcom/bin" and "palcom/lib". These will be the latest stable binaries. Developer tools: palcom/developer/dev-bin By using the "palcom/developer/dev-bin/pal-dev-*" scripts, one will instead invoke the latest build in your personal checkout. Requires full installation of Eclipse (see palcom/doc/setup/Eclipse-install.txt and palcom/doc/setup/Eclipse-SVN.txt) but allows for experiments with and development of the tools, including using Debug builds. Since the developer scripts are differently named than the regular scripts, adding both "palcom/bin" and "palcom/developer/dev-bin" to your PATH should pose no problems. palcom/developer Contains all sources, projects, resources etc. for the system