From 9c7a36e9acb6161693200b0bd0b9cd0ee4dbdb73 Mon Sep 17 00:00:00 2001 From: Olivier Berger Date: Wed, 9 Feb 2011 12:25:05 +0000 Subject: [PATCH] Adding explanation of configure-scripts.sh --- tools/VM-scripts/README.txt | 31 ++++++++++++++++++------------- 1 file changed, 18 insertions(+), 13 deletions(-) diff --git a/tools/VM-scripts/README.txt b/tools/VM-scripts/README.txt index 2d728f3..011c884 100644 --- a/tools/VM-scripts/README.txt +++ b/tools/VM-scripts/README.txt @@ -1,20 +1,25 @@ -See ~/Desktop/README.html which contains some docs. +The initial setup a user should do is : -See also : -https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/Virtual_machine_development_environment -for some more details. + # cd /root + # sh .../scripts/configure-scripts.sh BRANCH +where BRANCH is either 'Branch_5_1' or 'trunk' (without quotes) + +This will setup the ~/fusionforge "directory" (actually a link to the +wanted branch's checked-out copy), that should hold the to-be-tested +tested contents of the repository. -The ~/fusionforge "directory" should hold the to-be-tested tested -contents of the repository. +The 'fusionforge' symlink can be changed to point to another branch +checkout if you intend to have several branches under test in the same +VM. -It may conveniently be a soft link pointing to a trunk checkout or a -branch checkout if you intend to have several branches under test in -the same VM. +The 'scripts' "directory" is also a symlink to the tools/VM-scripts/ +dir inside the corresponding checked-out branch. -For instance, one may : -# cd ~ -# bzr checkout svn://scm.fusionforge.org/svnroot/fusionforge/trunk fusionforge-trunk -# ln -s fusionforge-trunk fusionforge +For using the other scripts see ~/Desktop/README.html which contains some docs. + +See also : +https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/Virtual_machine_development_environment +for some more details. -- Olivier Berger -- 2.1.4