[Bio] / ReleaseTools / README Repository:
ViewVC logotype

View of /ReleaseTools/README

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.2 - (download) (annotate)
Mon Dec 22 22:28:43 2003 UTC (16 years, 5 months ago) by efrank
Branch: MAIN
CVS Tags: mgrast_dev_08112011, mgrast_dev_08022011, rast_rel_2014_0912, rast_rel_2008_06_18, rast_rel_2008_06_16, mgrast_dev_04082011, Root-bobdev_news, merge-trunktag-bobdev_news-2, merge-trunktag-bobdev_news-1, rast_rel_2009_05_18, rast_rel_2009_0925, rast_rel_2010_0118, preTreatmanDyn, merge-trunktag-bodev_news-3, rast_rel_2009_02_05, rast_rel_2011_0119, rast_rel_2008_12_18, rast_rel_2008_10_09, rast_release_2008_09_29, mgrast_rel_2008_0919, rast_rel_2009_07_09, rast_rel_2011_0928, mgrast_rel_2008_0917, mgrast_dev_04052011, sc04-finalDay, merge-bodev_news-3, V00-00-07, V00-00-09, mobedac_release_05302012, V00-00-10, rast_rel_2010_0928, mgrast_version_3_2, gunk, caBIG-05Apr06-00, mgrast_dev_02212011, preSchematools, mgrast_rel_2008_0625, V00-00-12, V00-00-13, mgrast_release_3_0_4, V00-00-11, mgrast_release_3_0_2, mgrast_release_3_0_3, V00-00-14, V00-00-15, merge-bobdev_news-2, merge-bobdev_news-1, mgrast_dev_05262011, mgrast_rel_2008_0806, rast_rel_2008_08_07, myrast_33, rast_rel_2008_09_29, mgrast_dev_02222011, stMigration0, mgrast_dev_10262011, rast_rel_2008_11_24, sc2004-4, sc2004-3, sc2004-2, sc2004-1, sc2004-0, mgrast_dev_06072011, rast_rel_2008_09_30, before-dynamics-persistence, rast_rel_2008_10_29, rast_rel_2014_0729, mgrast_dev_03252011, mgrast_release_3_0, rast_rel_2010_1206, mgrast_rel_2008_0924, V00-00-08, lwc, mass-spec-01, mgrast_dev_03312011, mass-spec-03, mass-spec-02, mgrast_release_3_1_2, mgrast_release_3_1_1, mgrast_release_3_1_0, mgrast_dev_04132011, makeScriptHeaders, rast_rel_2008_07_21, mgrast_rel_2008_0923, mgrast_release_3_0_1, rast_rel_2010_0827, rast_rel_2009_03_26, rast_2008_0924, mgrast_dev_12152011, rast_rel_2010_0526, forRick-14Jul04-0, rast_rel_2008_04_23, caBIG-00-00-00, post-st-migration2, mgrast_rel_2008_1110_v2, mgrast_dev_04012011, treatman-lastDay-0, forRick-14Jul04-1, mgrast_rel_2008_1110, post-st-migration, caBIG-13Feb06-00, HEAD
Branch point for: Branch-bobdev_news
Changes since 1.1: +128 -3 lines

start instructions

Quick Users Guide


The ReleaseTools package provides tools for creating releases, importing
releases from other machines, and for making sandboxes for development
in.  These concepts are expanded below, then the tools are listed and

ReleaseTools supports a development process in which development is
done relative to a "release."  A release is simply a set of packages
that have been tested to work together. When you define a release, you
provide a list of package names and the CVS tag name for each that is
to be used. The release-creating tool, newrel, will check those packages
out for you into the release-install area and tune the directory

The work cycle looks like:
   o make a work directory.  put packages in there from CVS.
   o develop.
   o note, you may have more than one work directory, there are likely
     many developers, and they can be on multiple machines.
   o at some point, the group decides they want to sync and test as
     a system and "publish" a new release.  then
       - the group produces a set of packages and tag names for the release
       - someone does a newrel to define teh new release and to get
         it installed onto the release area of some machine.
       - people do importrel to import the release onto their machines.
         (importrel isn't client-server.  any two peers can do it.)


   RTROOT	Points to base of installation
   RTARCH       Architecture name, e.g., "mac" or "linux-posgres"
   RTCURRENT    Name of release you want to work on when you login. (can
                change later. 

Release Area:
   Where releases are installed.  It is  $RTROOT/dist/releases

Release Name:
   A name like 1.2.3
   You can have as many releases as you want installed into 

Work directory:
   A sandbox where you do development.  You create it with the command
   mkworkdir.  A sandbox knows a base release that you are developing


1. Getting user readyd for the first time.
   Set a few environment variables at login time.

	RTROOT=/home/fig/FIGdisk; export RTROOT
	RTARCH=linux-postgres; export RTARCH


    That should be it, but at the moment we have some other stuff.  There
    might be a source of a config from the release soon.

2. If you have a release already on your machine and want to develop against

   cd someplace where you want to work.  suppose the base release is 1.2.3.
   Give the commands,
	cd someplace
	mkworkdir -r 1.2.3 myNewSandboxName
	cd myNewSandboxName

3. How to put packages in there without haviong to know all the tags.
	cd mySandbox
	getPackage  <thePackageName>

   If you want to know all the packages in the release
	getPackage -l

   If you want them ALL checked out from cvs
	getPackage -a

4. How to import a new release
   Make sure you can write to $RTOOT/dist/releases.  Suppose the release
   you want to import is called 5.6.7 on host  thatPlace.gov

   importrel -r 5.6.7 -h thatPlace.gov

   Now you could do mkworkdir -r 5.6.7 myNewworkdir

5. How to make a new release

   Make sure you can write to $RTOOT/dist/releases. Create a file of
   the form below that lists all the packages and their tags that you
   want to have in the release:

ReleaseTools V00-00-05
FigCommon V00-00-01
FigKernelPackages V00-00-02
FigKernelScripts V00-00-01
FigPeer2PeerTools V00-00-00
FigWebPages V00-00-00
FigWebServices V00-00-02

    Suppose this file is called newReleaseDef.  Suppose you want to creatae
    a release called 6.7.8.  Give the command
    newrel  6.7.8 -f newReleaseDef

    You can now run importrel on other peers to get release 6.7.8

    NOTE:  newrel does not BUILD the release (compile it).  You have to 
    do a make.


MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3