-
Written by Scott,
-
-sharrison@users.sourceforge.net,
-January 17, 2001
-
Last updated, July 31, 2002
+Created: January 17, 2001
+
Last updated: February 28, 2011
-In order to log into CVS, CVS needs to be part of your system environment. +CVS needs to be part of your system environment in order to access the LON-CAPA CVS repository, You can do this by:
-export CVSROOT=:pserver:USERNAME@install.lon-capa.org:/home/cvs
+export CVS_RSH=ssh
+export CVSROOT=:ext:USERNAME@source.lon-capa.org:/home/cvs
-To actually login, you will need to execute the following command: -
-- -cvs login - -
--You are then prompted for a password. -If you do not have a password, or the password is not working, you -should contact helen@lon-capa.org. -
+The first time you use CVS, you need to CHECKOUT the repository. Generally speaking, you need to checkout loncapa only once @@ -85,14 +77,6 @@ To check-out the repository, use the cd loncapa
-After completing work with the CVS repository, -you can log out: -
-- -cvs logout - -
+cd loncom/build
+
make aboutVERSION
+
+General description of what happens +
++This is the actual make target code. +
+
+
+aboutVERSION:
+ cat $(SOURCE)/loncom/license/about.html | \
+ perl -e '$$d=`date +"%Y%m%d%H"`;chomp($$d);while(<>){s/(\<\!\-\- VERSION \-\-\>|\d+\.\d+\.CVS_HEAD\-\d{10})/$(SHOWVERSION)-$$d/; print;}' > \
+ $(SOURCE)/loncom/license/about.html.new
+ mv -v $(SOURCE)/loncom/license/about.html.new \
+ $(SOURCE)/loncom/license/about.html
+ cat $(SOURCE)/loncom/loncapa_apache.conf | \
+ perl -e '$$d=`date +"%Y%m%d%H"`;chomp($$d);while(<>){s/(\<\!\-\- VERSION \-\-\>|\d+\.\d+\.CVS_HEAD\-\d{10})/$(SHOWVERSION)-$$d/; print;}' > \
+ $(SOURCE)/loncom/loncapa_apache.conf.new
+ mv -v $(SOURCE)/loncom/loncapa_apache.conf.new \
+ $(SOURCE)/loncom/loncapa_apache.conf
+
+
++The LON-CAPA Version number is updated in the following files: +
+Updating the version information in these files means that visitors to the static HTML page: "About LON-CAPA" on your server will see which version of LON-CAPA you are running. The same information is also displayed on the dynamic log-in page generated by lonlogin.pm. Furthermore, the version of LON-CAPA running on your server can determine which course roles may be selectable on that server, if a course contains resource(s) and/or parameter(s) which require a specific version (or newer) of LON-CAPA. It is also possible for Domain Coordinators in another domain to configure their domain to limit hosting of sessions for users from their own domain to LON-CAPA servers in other domains which are running a specific LON-CAPA version (or newer). +
+On a development server, i.e., one where LON-CAPA is built and installed from a CVS checkout, running make aboutVERSION will cause the version number to be set to something of the form: M.N.CVS_HEAD-YYYYMMDDHH, where M.N will be the version number of the next stable (major) release (e.g., if the current stable release is 3.1; the next release would be 3.2), and YYYYMMDDHH is the datestamp when make aboutVERSION was last run. Note: make aboutVERSION will update the about.html and loncapa_apache.conf in the installation directory tree; it is not until make install is run that files served directly by the web server (or used for configuration) are updated with the versions in that tree. +
+Machine-specific information is the difference @@ -564,7 +590,7 @@ For safety reasons (so as to preserve a configuration files are NOT installed during this step. This means that files such as /etc/httpd/conf/loncapa.conf, /home/httpd/html/res/adm/includes/copyright.tab, and -/home/httpd/spare.tab are not overwritten, but remain as old, +/home/httpd/spare.tab are not overwritten, but remain as old, non-updated copies. (To automatically update these files and save/restore their encoded machine configuration, you must run "make configinstall").
@@ -659,7 +685,7 @@ RPM: BinaryRoot base_rpm_file_list cat $(SOURCE)/doc/loncapafiles/loncapafiles.lpml | \ perl lpml_parse.pl make_rpm $(CATEGORY) $(DIST) $(SOURCE) $(TARGET) \ > base_customizerpm.xml - cat base_rpm_file_list.txt | perl make_rpm.pl base 3.2 '' '' \ + cat base_rpm_file_list.txt | perl make_rpm.pl base 3.2 1 '' '' \ BinaryRoot base_customizerpm.xml BinaryRoot: base_rpm_file_list @@ -683,7 +709,7 @@ occur on the '/' filesystem location. span of months) and, unlike other automated RPM-builders, cleanly builds new RPMs without any after-effect of temporary files left on the system. The generated RPM is labeled in the format -LON-CAPA-base-(VERSION)-1.i386. VERSION is specified inside the +LON-CAPA-base-(VERSION)-(RELEASE).i386. VERSION is specified inside the Makefile.