Hello Henning, I go similar way as Alan does - I'm updating ConTeXt (usually) once a week while keeping backups of the previous versions.
My experience is that cca once a year I'm forced to get back to a previous Ctx copy as something stops working (IIRC, there some issues with switching to Lua 5.2 and now to Lua 5.3, an issue with Lua sorting alg which probably added a sortaity check at a point, a TickZ issue - all has been passed successfully over time (.dll rebuild with upper Lua releases, my fault in sorting alg, ...)), but some time later I "boarded" back to the "train-of-ConTeXt-beta-releases". I'm working on Windows (W7 and WX) - so for the case you were interested, I'm attaching some batches to save & update ConTeXt beta (call ReNew.bat from your Ctx installation direcory (d:\Ctx-Beta in my case); and also you need to have 7z installed which is used to zip the latest ConTeXt installation before update; .ba_ to be renamed to .bat). Best regards, Lukas On Fri, 09 Nov 2018 16:23:55 +0100, Alan Braslau <braslau.l...@comcast.net> wrote:
On Fri, 9 Nov 2018 15:05:59 +0100 Tomas Hala <tomas.h...@mendelu.cz> wrote:I solve the same problem for ages... I decided for fixed time pointsIf it may be useful: I keep a very short-term backup so that when things "break" or change, I can easily backtrack to a working copy. I update using the following shell script: #!/bin/sh CONTEXTHOME=${HOME}/context if [ ! -d ${CONTEXTHOME}/beta ] ; then mkdir -p ${CONTEXTHOME}/beta fi if [ ! -d ${CONTEXTHOME}/previous ] ; then mkdir -p ${CONTEXTHOME}/previous fi cd ${CONTEXTHOME}/beta echo "*** move current to previous ***" rsync -av --delete --progress . ../previous echo "*** update beta ***" rsync -ptv --progress rsync://contextgarden.net/minimals/setup/first-setup.sh . 2>&1 | tee first-setup.log ./first-setup.sh --modules=all --fonts=all --engine=luatex 2>&1 | tee -a first-setup.log This will not help against any undetected changes that may go unnoticed for a while between different projects, but does protect me against immediate "bugs". Hans has suggested keeping a ConTeXt standalone copy in each separate project file, as it is small enough that such duplication does not take up too much space. (As we strip-down the distribution and as storage space becomes bigger and bigger, this should not be a problem.) The advantage of having a copy associated with a project is that one can come back, years later even, and produce *exactly* the same output. Alan
-- Ing. Lukáš Procházka | mailto:l...@pontex.cz Pontex s. r. o. | mailto:pon...@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396
<<attachment: ReNewCtx~.zip>>
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
