Changeset 11611 for trunk/psconfig/INSTALL
- Timestamp:
- Feb 2, 2007, 6:55:36 PM (19 years ago)
- File:
-
- 1 edited
-
trunk/psconfig/INSTALL (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/psconfig/INSTALL
r10514 r11611 1 1 2 This is the top-level directory of the IPP software. here are a few 3 notes for installing IPP software in the correct order. A few things 4 to keep in mind: 2 The psconfig system allows the user to build and install the IPP 3 software suite into a location which is flexibly defined by the user. 4 The tools here also set up the user's environment variables (PATH, 5 PERL5LIB, LD_LIBRARY_PATH, etc) to make use of the installed 6 software. With the psconfig tools, it is easy to switch between 7 different installed versions or to recompile subsets of the IPP tree. 5 8 6 * three directories checked out here from CVS are mirrored from 7 external sources. DO NOT try to commit changes into those branches as 8 your commits will be lost when the repository is updated. The 9 directories to watch out for are: Ohana, psLib, psModules 9 NOTE: the psconfig.sh script uses the csh / tcsh shell. A bash version 10 is not currently available. 10 11 11 * the current (Jan 2006) tested versions of software depend on 12 specific tagged branches for certain components. if you have checked 13 this tree out of CVS, you will have to update those modules to their 14 branch tags. the following commands will bring you up to date with 15 those versions: 12 --- 16 13 17 cvs up -r eam_rel9_p0 psModules 18 cvs up -r eam_rel9_b1 psLib 14 Install Locations 19 15 20 required sequence: 16 To use the psconfig system, place the following line in your ~/.cshrc 17 file: 21 18 22 psLib 23 psModules 24 glueforge 25 metadatadb 26 ippTools/p2tools 19 alias psconfig "source PATH/psconfig.sh" 27 20 28 21 where PATH is the path to the file psconfig.sh in this directory 22 (ipp/psconfig/psconfig.sh). 29 23 30 -- 24 The psconfig system places the installed binary files by default in 25 directories below ~/psconfig. To use a different location, place the 26 following line in ~/.psconfigrc (otherwise not needed): 31 27 32 ** required PERL modules: 28 set PSCONFIG = INSTALL_PATH 33 29 34 Carp 35 Template 36 Statistics::Descriptive 37 Params::Validate 38 Parse::RecDescent 39 DateTime::Format::ISO8601 40 Class::Accessor::Fast 30 where INSTALL_PATH is the top-level directory for all binary 31 installations. 41 32 42 perl -MCPAN -e 'install MODULE' 33 Using psconfig to set / examine your install system: 43 34 44 http://search.cpan.org/ 35 psconfig: set or show the current pslib configuration information 36 USAGE: psconfig (version) : set configuration to specified version 37 psconfig --bin : return the current path 38 psconfig --libs : return the current library path 39 psconfig --list : list currently availabe configuration versions 40 psconfig --help : this listing 45 41 46 -- 42 --- 47 43 48 user-level installation of perl modules: 44 Building 49 45 50 * run cpan: 51 cpan 52 (answer questions to install in your home dir) 46 To build the full IPP tree using the psconfig system, run 'psbuild' in 47 this directory, and provide a release version. (NOTE: if you are 48 building from a checked-out tarball, the CVS tags are not used, and 49 you will not be able to use the update. 53 50 54 # install packages:55 cpan Carp56 cpan Template57 cpan Statistics::Descriptive58 cpan Params::Validate59 cpan Parse::RecDescent60 cpan DateTime::Format::ISO860161 cpan Class::Accessor::Fast
Note:
See TracChangeset
for help on using the changeset viewer.
