--- doc/build/Attic/cvsupgrade.html 2001/04/18 16:48:04 1.2 +++ doc/build/Attic/cvsupgrade.html 2001/09/05 22:03:30 1.5 @@ -6,7 +6,7 @@

LON-CAPA CVS Upgrade

Current CVS Upgrade Procedure

-Scott Harrison +Scott Harrison, last updated 05/19/2001

Last updated: 4/18/2001 @@ -38,7 +38,7 @@ upgrading your system is a simple proces export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs
cvs login Go to your repository directorycd loncapa -Update your CVS sourcescvs update -d +Update your CVS sourcescvs update -d -r STABLE Go to the build directorycd loncom/build Become 'root'su Install/update static filesmake install @@ -59,7 +59,10 @@ enter this command twice. Restarting th /etc/rc.d/init.d/loncontrol restart After CVS logging in, you can always cut and paste this line below assuming you do everything as root :)
-cd loncapa; cvs update -d; cd loncom/build; make install; make configinstall; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/loncontrol restart +cd loncapa; cvs update -d -r STABLE; cd loncom/build; make install; make +configinstall; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd +restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/loncontrol restart +

It may be also advisable to test your system after an upgrade if there are @@ -148,7 +151,7 @@ RedHat 6.2 bugs involving enlightenment export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs
cvs login Go to your repository directorycd loncapa -Update your CVS sourcescvs update -d +Update your CVS sourcescvs update -d -r STABLE Go to the build directorycd loncom/build Become 'root'su View the CVS source->install status of your machinemake statuspost @@ -165,6 +168,11 @@ then visit http://MACHINENAME/lon-status These instructions assume bash (as opposed to tcsh).

+You will also need an account on zaphod.lite.msu.edu. +Please e-mail lon-capa@hobbes.lite.msu.edu and request that +an account be created. +

+

The straightforward way to enable CVS is to manually configure your environment and log in:

@@ -211,7 +219,8 @@ Useful commands are: CommandDescription info cvsdoc's cvs log FILENAMEsee what's happened with a file -cvs update -dupdate your CVS tree from the current directory location +cvs update -d -r STABLEupdate your CVS tree from the +current directory location