[Gusdev-gusdev] schema.prop

[Chetna W. <ch...@ar...>]

Hi,

I installed Ant 1.5.1 and the isfalse problem seems to disappear. 
What are the changes in the install.prop? It would be great if someone can
give insight.
I am pasting the following:

[chetna@mango install]$ build GUS install -append

ant -f /home/projects/install/build.xml install -Dproj=GUS
-DtargetDir=/home/gus_home -Dcomp= -DprojectsDir=/home/projects
-Dappend=true -logger org.apache.tools.ant.NoBannerLogger | grep ']'


BUILD FAILED
file:/home/projects/install/build.xml:228:
      Error: You must configure the file
/home/gus_home/config/install.prop.  To create it, copy
/home/gus_home/config/install.prop.sample to
/home/gus_home/config/install.prop and edit
/home/gus_home/config/install.prop, giving it the proper values for your
installation.


Total time: 1 second
[chetna@mango install]$

Hope to hear from you
Chetna


> I've tested the GUS 3.0 schema creation scripts and have tagged the
> current release in CVS as 'schema30-code10' (i.e., GUS schema version
> 3.0, code version 1.0.)  Here's the install process in a nutshell:
> 
>  1. Install the GUS code as described on the gusdb.org web site
>     (at <http://www.gusdb.org/BuildSystemSetup.html>)  During the
>     installation the build system should tell you to create the
>     properties file $GUS_HOME/config/schema.prop;  this file
>     should be edited in order to customize the schema installation
>     scripts to your site and Oracle database instance.
> 
>     (As an aside, if you don't want to place the Oracle SYS password
>     in this file, you can instead choose to run the schema creation
>     scripts manually, since only of the scripts must be run with
>     SYS/DBA privileges.  In fact, now that I think of it, the script
>     in question could be run by any user with the ability to create
>     user accounts.  I'll put changing this on the to-do list.)
> 
>  2. Once the install is complete, cd to $GUS_HOME/schema/oracle
>  3. Make sure that the Oracle utility 'sqlplus' is in your $PATH.
>  4. Make sure that $GUS_HOME/bin is in your path and that you can
>     execute the scripts therein.
> 
>     (Another aside; not all of the scripts have been updated to
>     the new Perl package structure, but the only one we care
>     about for this step is grantPermissions.pl and you can try
>     running it on the command line--it should display a short
>     usage message if successful.)
> 
>  5. Review $GUS_HOME/schema/oracle/create-db.sh to make sure that
>     it's not going to do anything that you're unhappy with...
>  6. Run ./create-db.sh (Or, if you're using the manual install method,
>     run the commands contained in this file in the order given.)
>  7. Check that all of the scripts and/or commands in create-db.sh
>     ran successfully.
> 
>     (This step still needs to be automated.  For now you can either
>     query the Oracle system tables to check that the correct number
>     of uses/tables/etc. were created, or grep the .log files for the
>     same information.  At the end of each .sql file is a line stating
>     how many CREATE statements are in that file, which can be compared
>     to the query or grep results.)
> 
> I won't be in the lab. tomorrow/today (Friday) but people in the lab.
> should be able to reach me by mobile phone if there are any questions
> or problems.
> 
> Jonathan
> 
>