1
0
mirror of synced 2026-01-25 20:06:44 +00:00

Remove now obsolete sources/*.CM files; update README a bit

This commit is contained in:
Frank Halasz
2023-08-02 01:02:12 -07:00
committed by Larry Masinter
parent b0ec2476d5
commit ae2633591e
6 changed files with 17 additions and 33 deletions

View File

@@ -7,18 +7,30 @@ Loading from an old 'starter' sysout
* loadup-mid-from-init.sh -- phase 2 (creates init.sysout)
* loadup-lisp-from-mid.sh -- phase 3 (creates lisp.sysout)
* loadup-full-from-lisp.sh -- phase 4 (creates full.sysout)
* loadup-aux.sh -- phase 5,(creates exports.all whereis.hash
* loadup-apps-from-full.sh -- phase 5 (creates app.sysout, with notecards, rooms and clos; optional)
* loadup-aux.sh -- phase 6 (creates exports.all whereis.hash)
* loadup-db-from-full.sh -- phase 7 (makes unreleased 'fuller.sysout' and fuller.database)
* loadup-full.sh -- Phase 1-4 only
All of these scripts read from and write to a directory specified by the env variable LOADUP_WORKDIR.
LOADUP_WORKDIR defaults to /tmp/loadups-$$ (where $$ is the PID of the script). Note that all /tmp files
are cleared after 10 days or upon system reboot. You can replicate the old work directory scheme
where files were never deleted automatically by simply setting LOADUP_WORKDIR to "./tmp"
* loadup-db.sh -- phase 6 (makes unreleased 'fuller.sysout' and fuller.database
* copy-all.sh -- copy loadups from tmp/ to loadups/ and library/
* loadup-all.sh [-apps] -- Phases 1-4 & 6 (plus Phase 5 with -apps flag)
* loadup-db.sh -- phase 7 only based on full.syout in loadup directory
These two scripts call the 7 scripts above as specified and then (if successful) copy (ln) the results
to the loadups directory using a versioned copy. The files are hardlinked into loadups from the workdir
if workdir and loadups are on the same filesystem, otherwise they are copied.
* loadup-full.sh -- Phases 1-4 only, no copy into loadups at the end.
## possibly handy scripts
* lsee <lispfile> -- show lisp file with font-control-characters rendered as linux color changes
* cpv file1 file2 -- copies file1 to file2 (or directory name) adding versions
* cpv file1 file2 -- hardlinks (or copies) file1 to file2 (or directory name) adding versions
choice of hardlink or copy depends on whether the files are on the same filesystem.
* restore-versions.sh -- pulls out old versions from git history and links in with medley versioning conventions
## Not useful anymore