Commit by: bear Modified files: internal/installers/win/README.txt 1.2 1.3 internal/installers/rpm/README.txt 1.1 1.2
Log message: updating README'sy ViewCVS links: http://cvs.osafoundation.org/index.cgi/internal/installers/win/README.txt.diff?r1=text&tr1=1.2&r2=text&tr2=1.3 http://cvs.osafoundation.org/index.cgi/internal/installers/rpm/README.txt.diff?r1=text&tr1=1.1&r2=text&tr2=1.2 Index: internal/installers/win/README.txt diff -u internal/installers/win/README.txt:1.2 internal/installers/win/README.txt:1.3 --- internal/installers/win/README.txt:1.2 Tue Feb 8 20:55:35 2005 +++ internal/installers/win/README.txt Tue Mar 8 11:58:57 2005 @@ -1,8 +1,8 @@ # # Chandler Win32 Installer README.txt # -# $Revision: 1.2 $ -# $Date: 2005/02/09 04:55:35 $ +# $Revision: 1.3 $ +# $Date: 2005/03/08 19:58:57 $ # Copyright (c) 2004,2005 Open Source Applications Founation # http://osafoundation.org/Chandler_0.1_license_terms.htm # @@ -17,6 +17,12 @@ Compiling setup.exe under Windows + NOTE: if you are running the build process under Cygwin, + there is a helper script in internal/installers/win + called makeinstallers.sh that checks the setup, calls + makensis and then copies and renames Setup.exe to the + tinderbuild working directory. + 1. create an installation image of Chandler in a build directory 2. place in the build directory the chandler.nsi script 3. change to the build directory @@ -36,7 +42,7 @@ /path/to/makesys chandler.nsi 5. the Setup.exe will created in the build directory - + Installing NSIS on Linux 1. extract the nsis204.tar.bz2 tarball Index: internal/installers/rpm/README.txt diff -u internal/installers/rpm/README.txt:1.1 internal/installers/rpm/README.txt:1.2 --- internal/installers/rpm/README.txt:1.1 Mon Dec 6 22:11:10 2004 +++ internal/installers/rpm/README.txt Tue Mar 8 11:58:57 2005 @@ -1,16 +1,12 @@ # # Chandler RPM Installer README.txt # -# $Revision: 1.1 $ -# $Date: 2004/12/07 06:11:10 $ +# $Revision: 1.2 $ +# $Date: 2005/03/08 19:58:57 $ # Copyright (c) 2004 Open Source Applications Founation # http://osafoundation.org/Chandler_0.1_license_terms.htm # -NOTE: This is a test RPM - it has been tested only on a basic - FC2 setup and has not been tested to ensure a clean - un-install - To build the binary RPM, you need to do the following: First, create a rpm build environment that will let you test @@ -31,34 +27,19 @@ %_topdir /home/whatever_user_name_where_rpm_lives/rpm - 3. create a temp dir to extract and "massage" the chandler distribution - - mkdir osaf_temp - -Once the above is ready, then you can retrieve the distribution tarball -you want to build the binary RPM from and prepare it. These steps will -very soon be scripted so that they are done by the hardhat and/or tinderbox -scripts. - - 1. cd /path/to/osaf_temp - 2. mkdir usr - mkdir usr/local - 3. cd usr/local - 4. tar xvzf Chandler_debug_foo.tar.gz - 5. cd ../.. - 6. tar zcvf ~/rpm/SOURCES/chandler.tar.gz usr - -Note that currently the chandler.spec file has a number of hard-coded -entries. The plan is to replace them with references to defines that -are created by a wrapper script. +After you have setup the RPM environment, you can create the RPM by +running the makeinstaller.sh helper script. This script is what is +run within the Hardhat/Tinderbox environment so it has some assumptions. + +Running internal/installers/rpm/makeinstaller.sh without any command +line parameters will give you the following usage help: + + usage: $0 <path to .spec file> <.spec file> <path to distrib directory> <distrib file root> + + example: $0 /home/builder/tinderbuild/internal/installers/rpm/ chandler.spec /home/builder/tinderbuild/ Chandler_linux_foo + +This script will check the rpm setup, copy the distribution tarball from +the tinderbuild working directory, setup the proper SOURCES/ tree, call +rpmbuild and then finally copy and rename the rpm to the tinderbuild +working directory. -Once the SOURCES tarball is created, now it's time to tell rpmbuild to -do it's thing. - - rpmbuild -ba chandler.spec - -Note that you will see a number of dependency errors - these are expected -at this stage. - -After rpmbuild runs, you will find a binary RPM in ~/rpm/RPMS/i386/ that -is named Chandler-0.4-1.i386.rpm _______________________________________________ Commits mailing list Commits@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/commits
