doc/build/cvsupgrade.html - diff

Return to cvsupgrade.html CVS log

Up to [LON-CAPA] / doc / build

Diff for /doc/build/Attic/cvsupgrade.html between versions 1.2 and 1.6

version 1.2, 2001/04/18 16:48:04	version 1.6, 2001/11/08 16:42:49
Line 6	Line 6
<h1>LON-CAPA CVS Upgrade</h1>	<h1>LON-CAPA CVS Upgrade</h1>
<h3>Current CVS Upgrade Procedure</h3>	<h3>Current CVS Upgrade Procedure</h3>
<p>	<p>
Scott Harrison	Scott Harrison, last updated 11/7/2001
</p>
<p>
Last updated: 4/18/2001
</p>	</p>
<ul>	<ul>
<li><a href="#fileupgrade">CVS Upgrade</a></li>	<li><a href="#fileupgrade">CVS Upgrade</a></li>
Line 38 upgrading your system is a simple proces	Line 35 upgrading your system is a simple proces
<td>export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs	<td>export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs
<br />cvs login</td></tr>	<br />cvs login</td></tr>
<tr><td>Go to your repository directory</td><td>cd loncapa</td></tr>	<tr><td>Go to your repository directory</td><td>cd loncapa</td></tr>
<tr><td>Update your CVS sources</td><td>cvs update -d</td></tr>	<tr><td>Update your CVS sources</td><td>cvs update -d -r STABLE</td></tr>
<tr><td>Go to the build directory</td><td>cd loncom/build</td></tr>	<tr><td>Go to the build directory</td><td>cd loncom/build</td></tr>
<tr><td>Become 'root'</td><td>su</td></tr>	<tr><td>Become 'root'</td><td>su</td></tr>
<tr><td>Install/update static files</td><td>make install</td></tr>	<tr><td>Install/update static files</td><td>make install</td></tr>
Line 59 enter this command twice. Restarting th	Line 56 enter this command twice. Restarting th
<td>/etc/rc.d/init.d/loncontrol restart</td></tr>	<td>/etc/rc.d/init.d/loncontrol restart</td></tr>
<tr><td colspan=2>After CVS logging in, you can always cut and paste this line	<tr><td colspan=2>After CVS logging in, you can always cut and paste this line
below assuming you do everything as root :)<br />	below assuming you do everything as root :)<br />
<tt>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</tt></td></tr>	<tt>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
	</tt></td></tr>
</table>	</table>
<p>	<p>
It may be also advisable to test your system after an upgrade if there are	It may be also advisable to test your system after an upgrade if there are
Line 111 and CVS:doc/otherfiles/cd_rpms.txt.	Line 111 and CVS:doc/otherfiles/cd_rpms.txt.
<b>Upgrade existing RPMS from a trusted source:</b>	<b>Upgrade existing RPMS from a trusted source:</b>
RPMs are currently available at	RPMs are currently available at
<blockquote>	<blockquote>
http://install.lon-capa.org/3.1/currentcdsource/RedHat/RPMS	http://install.lon-capa.org/3.1/latestRPMS/
</blockquote>	</blockquote>
For example, to upgrade your LON-CAPA-systemperl RPM, you	For example, to upgrade your LON-CAPA-systemperl RPM, you
would enter commands like	would enter commands like
<blockquote>	<blockquote>
wget http://install.lon-capa.org/3.1/currentcdsource/RedHat/RPMS/LON-CAPA-systemperl-3.1-1.i386.rpm<br />	wget http://install.lon-capa.org/3.1/currentcdsource/RedHat/RPMS/LON-CAPA-systemperl-3.2-1.i386.rpm<br />
(then as root) rpm -Uvh --force LON-CAPA-systemperl-3.1-1.i386.rpm	(then as root) rpm -Uvh --force LON-CAPA-systemperl-3.1-1.i386.rpm
</blockquote>	</blockquote>
</p>	</p>
Line 148 RedHat 6.2 bugs involving enlightenment	Line 148 RedHat 6.2 bugs involving enlightenment
<td>export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs	<td>export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs
<br />cvs login</td></tr>	<br />cvs login</td></tr>
<tr><td>Go to your repository directory</td><td>cd loncapa</td></tr>	<tr><td>Go to your repository directory</td><td>cd loncapa</td></tr>
<tr><td>Update your CVS sources</td><td>cvs update -d</td></tr>	<tr><td>Update your CVS sources</td><td>cvs update -d -r STABLE</td></tr>
<tr><td>Go to the build directory</td><td>cd loncom/build</td></tr>	<tr><td>Go to the build directory</td><td>cd loncom/build</td></tr>
<tr><td>Become 'root'</td><td>su</td></tr>	<tr><td>Become 'root'</td><td>su</td></tr>
<tr><td>View the CVS source->install status of your machine</td><td>make statuspost	<tr><td>View the CVS source->install status of your machine</td><td>make statuspost
Line 165 then visit http://MACHINENAME/lon-status	Line 165 then visit http://MACHINENAME/lon-status
These instructions assume bash (as opposed to tcsh).	These instructions assume bash (as opposed to tcsh).
</p>	</p>
<p>	<p>
	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.
	</p>
	<p>
The straightforward way to enable CVS is to manually configure your	The straightforward way to enable CVS is to manually configure your
environment and log in:	environment and log in:
<blockquote>	<blockquote>
Line 211 Useful commands are:	Line 216 Useful commands are:
<tr><td>Command</td></td><td>Description</td></tr>	<tr><td>Command</td></td><td>Description</td></tr>
<tr><td>info cvs</td></td><td>doc's</td></tr>	<tr><td>info cvs</td></td><td>doc's</td></tr>
<tr><td>cvs log FILENAME</td></td><td>see what's happened with a file</td></tr>	<tr><td>cvs log FILENAME</td></td><td>see what's happened with a file</td></tr>
<tr><td>cvs update -d</td></td><td>update your CVS tree from the current directory location</td></tr>	<tr><td>cvs update -d -r STABLE</td></td><td>update your CVS tree from the
	current directory location</td></tr>
</table>	</table>
</body>	</body>
</html>	</html>

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>

Removed from v.1.2
changed lines
	Added in v.1.6