[Koha-devel] CVS: koha installer.pl,1.2,1.2.2.1

[Pat Eyler]

Update of /cvsroot/koha/koha
In directory usw-pr-cvs1:/tmp/cvs-serv9937

Modified Files:
      Tag: rel-1-2
	installer.pl 
Log Message:
more markup of spots to look at

Index: installer.pl
===================================================================
RCS file: /cvsroot/koha/koha/installer.pl,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -C2 -r1.2 -r1.2.2.1
*** installer.pl	21 Apr 2002 01:58:26 -0000	1.2
--- installer.pl	26 Apr 2002 14:47:17 -0000	1.2.2.1
***************
*** 1,4 ****
--- 1,5 ----
  #!/usr/bin/perl -w # please develop with -w
  
+ 
  use strict; # please develop with the strict pragma
  
***************
*** 13,17 ****
  This installer will prompt you with a series of questions.
  It assumes you (or your system administrator) has installed:
!   * Apache (http://www.apache.org)
    * Perl (http://www.perl.org)
  
--- 14,18 ----
  This installer will prompt you with a series of questions.
  It assumes you (or your system administrator) has installed:
!   * Apache (http://httpd.apache.org/)
    * Perl (http://www.perl.org)
  
***************
*** 25,30 ****
  
  
! Is Apache, Perl, and a database from the list above installed on this system?
! 
  EOM
  
--- 26,31 ----
  
  
! Are Apache, Perl, and a database from the list above installed 
! on this system? (Y/[N]):
  EOM
  
***************
*** 43,46 ****
--- 44,52 ----
    };
  
+ 
+ #
+ #  Hmm, on further thought, this file came out of the tarball ... so
+ #  is it likely to be untarred again?
+ #
  print "I need to unpack the Koha TarFile -- where is it?  ";
  $answer = $_;
***************
*** 53,71 ****
  
  #test for Perl and Apache?
! print "Are you using MySql?[Y/N]: ";
  $answer = $_;                      
  chomp $answer
! if ($answer eq "Y") { 
! 	system("mysqladmin -uroot -ppassword create $KohaDBNAME ");
! 	system("mysql -u$root -p$password ");
! 	#need to get to mysql prompt  HOW DO I DO THIS?
! 
! 	# FIXME 
! 	# you could pipe this into mysql in the shell that system generates
! 	# can this be done from dbi?
! 	system("grant all privileges on Koha.* to koha at localhost identified by 'kohapassword'; ");
! 
!   };
! if ($answer eq "N") {
      print <<EOM;
  You will need to use the MySQL database system for your application.
--- 59,77 ----
  
  #test for Perl and Apache?
! print "Are you using MySql?(Y/[N]): ";
  $answer = $_;                      
  chomp $answer
! if ($answer eq "Y" || $answer eq "y") {
!     # FIXME
!     # there is no $password or $KohaDBNAME yet
!     system("mysqladmin -uroot -p$password create $KohaDBNAME ");
!     system("mysql -u$root -p$password ");
!     #need to get to mysql prompt  HOW DO I DO THIS?
!     
!     # FIXME 
!     # you could pipe this into mysql in the shell that system generates
!     # can this be done from dbi?
!     system("grant all privileges on Koha.* to koha at localhost identified by 'kohapassword'; ");
! } else {
      print <<EOM;
  You will need to use the MySQL database system for your application.
***************
*** 75,84 ****
  
  print "\n";
  system ("perl updatedatabase -I /pathtoC4 ");
  
  #KOHA conf
  # FIXME
  # is there a reason we don't just create the conf file here?
! 
  print <<EOM;
  You will need to add the following to the Koha configuration file\n";
--- 81,99 ----
  
  print "\n";
+ #
+ # FIXME
+ # there is no updatedatabase program yet
+ #
  system ("perl updatedatabase -I /pathtoC4 ");
  
  #KOHA conf
+ 
  # FIXME
  # is there a reason we don't just create the conf file here?
! # We could ask where the file is to be kept, update our 
! # scripts to look for it there, and just write out to the
! # new file (possibly allowing the installer.pl user to edit the
! # file first).
! #
  print <<EOM;
  You will need to add the following to the Koha configuration file\n";
***************
*** 89,92 ****
--- 104,115 ----
  includes=/usr/local/www/koha/htdocs/includes\n";
  EOM
+ 
+ 
+ # FIXME
+ # Again, this may be something to automate.  We could ask a 
+ # series of questions, then fill out a form with the answers and 
+ # edit the existing config file in place.  (Again, giving the
+ # installer.pl user a chance to edit the file first.)
+ #
  
  #SETUP opac