Update build notes for use with GIT, not SVN

BUILD.NOTES

@@ -23,9 +23,11 @@ then check-in the new Makefile.am and Makefile.in files
 
 Here is a step-by-step HOWTO for creating a new release of SLURM on a
 Linux cluster (See BlueGene and AIX specific notes below for some differences).
-0. svn co https://eris.llnl.gov/svn/slurm/trunk slurm
-   svn co https://eris.llnl.gov/svn/chaos/private/buildfarm/trunk buildfarm
-   put the buildfarm directory in your search path
+0. Get current copies of SLURM and buildfarm
+   > git clone https://<user_name>@github.com/chaos/slurm.git
+   > svn co https://eris.llnl.gov/svn/chaos/private/buildfarm/trunk buildfarm
+   place the buildfarm directory in your search path
+   > export PATH=~/buildfarm:$PATH
 1. Update NEWS and META files for the new release. In the META file,
    the API, Major, Minor, Micro, Version, and Release fields must all
    by up-to-date. **** DON'T UPDATE META UNTIL RIGHT BEFORE THE TAG ****
@@ -35,39 +37,36 @@ Linux cluster (See BlueGene and AIX specific notes below for some differences).
      files, but not to code.
    - this is a prerelease (Release = 0.preX)
 2. Tag the repository with the appropriate name for the new version.
-   svn copy https://eris.llnl.gov/svn/slurm/trunk \
-     https://eris.llnl.gov/svn/slurm/tags/slurm-1-2-0-0-pre3 \
-     -m "description"
+   > git tag -a slurm-2-3-0-0-pre5 -m "create tag v2.3.0-pre5"
+   > git push --tags
 3. Use the rpm make target to create the new RPMs. This requires a .rpmmacros 
    (.rpmrc for newer versions of rpmbuild) file containing:
 	%_slurm_sysconfdir      /etc/slurm
 	%_with_debug            1
 	%_with_sgijob		1
 	%_with_elan		1   (ONLY ON SYSTEMS WITH ELAN SWITCH)
-   I usually build with using the following syntax:
-   build  -s https://eris.llnl.gov/svn/slurm/tags/slurm-1-2-0-0-pre3
+   Build using the following syntax:
+   > build  --snapshot   -s <local_dir>  OR
+   > build  --nosnapshot -s <local_dir>
+   --nosnapshot will name the tar-ball and RPMs based upon the META file
+   --snapshot  will name the tar-ball and RPMs based upon the META file plus a
+   timestamp
 4. Remove the RPMs that we don't want:
-   rm -f slurm-perlapi*rpm slurm-torque*rpm
+   > rm -f slurm-perlapi*rpm slurm-torque*rpm
 5. Move the RPMs to
    /usr/local/admin/rpms/llnl/RPMS-RHEL4/x86_64 (odevi, or gauss)
    /usr/local/admin/rpms/llnl/RPMS-RHEL4/i386/ (adevi)
    /usr/local/admin/rpms/llnl/RPMS-RHEL4/ia64/ (tdevi)
    send an announcement email (with the latest entry from the NEWS
    file) out to linux-admin@lists.llnl.gov.
-6. Copy tagged bzip file (e.g. slurm-0.6.0-0.pre3.bz2) to FTP server
-   for external SLURM users.
-7. Copy bzip file and rpms (including src.rpm) to sourceforge.net:
-   ncftp upload.sf.net
-   cd upload
-   put filename
-   Use SourceForge admin tool to add new release, including changelog.
+6. Copy bzip file to sourceforge.net using their web interface
 
 BlueGene build notes:
 0. If on a bgp system and you want sview export these variables
-    export CFLAGS="-I/opt/gnome/lib/gtk-2.0/include -I/opt/gnome/lib/glib-2.0/include $CFLAGS"
-    export LIBS="-L/usr/X11R6/lib64 $LIBS"
-    export CMD_LDFLAGS='-L/usr/X11R6/lib64'
-    export PKG_CONFIG_PATH="/opt/gnome/lib64/pkgconfig/:$PKG_CONFIG_PATH"
+   > export CFLAGS="-I/opt/gnome/lib/gtk-2.0/include -I/opt/gnome/lib/glib-2.0/include $CFLAGS"
+   > export LIBS="-L/usr/X11R6/lib64 $LIBS"
+   > export CMD_LDFLAGS='-L/usr/X11R6/lib64'
+   > export PKG_CONFIG_PATH="/opt/gnome/lib64/pkgconfig/:$PKG_CONFIG_PATH"
 1. Use the rpm make target to create the new RPMs. This requires a .rpmmacros
    (.rpmrc for newer versions of rpmbuild) file containing:
 	%_prefix                /usr
@@ -76,13 +75,17 @@ BlueGene build notes:
 	%_without_pam		1
 	%_with_debug            1
    Build on Service Node with using the following syntax
-   rpmbuild -ta slurm-...bz2
+   > rpmbuild -ta slurm-...bz2
    The RPM files get written to the directory
    /usr/src/packages/RPMS/ppc64
 
 To build and run on AIX:
-0. svn co https://eris.llnl.gov/svn/slurm/trunk slurm
-   svn co https://eris.llnl.gov/svn/buildfarm/trunk buildfarm
+0. Get current copies of SLURM and buildfarm
+   > git clone https://<user_name>@github.com/chaos/slurm.git
+   > svn co https://eris.llnl.gov/svn/chaos/private/buildfarm/trunk buildfarm
+   put the buildfarm directory in your search path
+   > export PATH=~/buildfarm:$PATH
+
    Put the buildfarm directory in your search path
    Also, you will need several commands to appear FIRST in your PATH:
 
@@ -93,10 +96,11 @@ To build and run on AIX:
    I do this by making symlinks to those commands in the buildfarm directory,
    then making the buildfarm directory the first one in my PATH.
    Also, make certain that the "proctrack" rpm is installed.
-1. export OBJECT_MODE=32
-   export PKG_CONFIG="/usr/bin/pkg-config"
+1. Export some environment variables
+   > export OBJECT_MODE=32
+   > export PKG_CONFIG="/usr/bin/pkg-config"
 2. Build with:
-   ./configure --enable-debug --prefix=/opt/freeware \
+   > ./configure --enable-debug --prefix=/opt/freeware \
 	--sysconfdir=/opt/freeware/etc/slurm \
 	--with-ssl=/opt/freeware --with-munge=/opt/freeware \
 	--with-proctrack=/opt/freeware
@@ -120,10 +124,10 @@ To build and run on AIX:
 	%with_proctrack         "--with-proctrack=/opt/freeware"
    Log in to the machine "uP".  uP is currently the lowest-common-denominator
      AIX machine.
-   CC=/usr/bin/gcc build -s https://eris.llnl.gov/svn/slurm/tags/slurm-1-2-0-0-pre3
-4. export MP_RMLIB=./slurm_ll_api.so
-   export CHECKPOINT=yes
-5. poe hostname -rmpool debug
+   > CC=/usr/bin/gcc build -s https://eris.llnl.gov/svn/slurm/tags/slurm-1-2-0-0-pre3
+4. > export MP_RMLIB=./slurm_ll_api.so
+   > export CHECKPOINT=yes
+5. > poe hostname -rmpool debug
 6. To debug, set SLURM_LL_API_DEBUG=3 before running poe - will create a file
      /tmp/slurm.*
    It can also be helpful to use poe options "-ilevel 6 -pmdlog yes"