Contents of /meta-cvs/F-450C02688626772DFA468E0E08C03476
| Revision Log
Mon Oct 21 04:48:14 2002 UTC
(11 years, 1 month ago)
CVS Tags: asdf-import-branch~merged-to-HEAD-0, mcvs-1-1-98, asdf-import-branch~branch-point, mcvs-1-1-0, mcvs-1-0-3, HEAD
Branch point for: asdf-import-branch
Changes since 1.1: +25 -0 lines
Merging from mcvs-1-0-branch
Fix broken ``filt -r''.
* code/mapping.lisp (mapping-read-raw-map): New function; reads
map from stream and does sanity check.
(mapping-read): Argument can be a filename or stream. Call to
mapping-read-raw-map to factor out common code for both cases.
* code/filt.lisp (filt-select-map): This was still just
reading the raw structure from the cvs coprocess, which worked under
the old map format, when the internal and external representations
were the same. Now it calls mapping-read on the stream.
* UPGRADE-EXISTING: New file.
* code/mcvs-main.lisp: Clear out *modules* list before requiring
modules. This is needed so that mcvs-upgrade works, because there
is already a populated list in the Lisp image.
|| Upgrading Meta-CVS
||If you already have an installation of Meta-CVS which includes the mcvs-upgrade
||command, then you can upgrade the program from the source code, even if you
||installed a binary distribution of Meta-CVS, and don't have any tools required
||to build it.
||Meta-CVS carries with it the Lisp compiler that is used to compile it, as well
||as the custom Lisp executable with some C code. The upgrade method assumes that
||the new Meta-CVS source code does not rely on any new C functions added the
||lisp.run executable. If the new version of the code needs new C functions, then
||this upgrade method will not work.
||The procedure is simple. Run the ``mcvs-upgrade'' command, giving it a single
||argument---the name of the directory where your Meta-CVS source code resides.
||This should be that directory in which the file mcvs-main.lisp is found, wich
||is currently the code/ subdirectory of the Meta-CVS source tree.
||Upgrading will produce a lot of warnings, because it works by loading new
||versions of code into an existing Lisp image, causing functions and variables
||to be replaced with new ones. Just ignore the warnings, and pay attention to
||the last message, which states whether or not the upgrade succeeded.
||After that when you run ``mcvs --version'' it should show the new version