From: Bruce Horrocks <ntg@scorecrow.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: Rolling out a pandoc-context publication workflow in an organization
Date: Fri, 2 Jul 2021 00:07:22 +0100 [thread overview]
Message-ID: <C2C75C64-FBE4-4963-98F5-B7C4C4D27AB5@scorecrow.com> (raw)
In-Reply-To: <08c5fc66-4b32-97fe-3ded-6ffe71b666c1@mailbox.org>
On 1 Jul 2021, at 07:02, Jan U. Hasecke <juh+ntg-context@mailbox.org> wrote:
>
> If we use the current lmtx distribution, all editors would have to install ConTeXt with the install.sh script on their private computers, then we would either call a post installation script to clone the repositories in texmf-project or to clone them in another folder and set links to texmf-project. Linking seems better as I am not sure what "context generate" would do with the .git folder inside the repositories.
One option you might try, if your cooperative has a web-server available to editors, is to store your own ConTeXt repository. That way you can update the LMTX version when you are ready to.
This works because "install.sh" can have a "--server" parameter supplied. By default it goes to lmtx.pragma-ade.com/install-lmtx but if you were to copy the install-lmtx directory and host the copy on your own server at the same path, then you could 'freeze' your LMTX version until you were ready to change.
Since editors might run the install.sh themselves, you would probably want to tweak your local copy of install.sh to only install from your own server.
When a new version of LMTX comes out, and when you have the time, you can install normally on a test machine and run whatever regression tests you want. Once happy you take a fresh copy of "https://lmtx.pragma-ade.com/install-lmtx/texmf-context.zip" onto your server and ask your editors to run install.sh at their own convenience.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-07-01 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 6:02 Jan U. Hasecke
2021-07-01 6:44 ` Taco Hoekwater
2021-07-01 11:31 ` Jan U. Hasecke
2021-07-01 12:00 ` Taco Hoekwater
2021-07-01 11:47 ` Aditya Mahajan
2021-07-01 23:07 ` Bruce Horrocks [this message]
2021-07-02 7:38 ` Jan U. Hasecke
2021-07-02 8:42 ` Hans Hagen
2021-07-02 9:56 ` Jan U. Hasecke
2021-07-02 11:17 ` Hans Hagen
2021-07-02 15:35 ` Aditya Mahajan
2021-07-02 7:49 ` denis.maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2C75C64-FBE4-4963-98F5-B7C4C4D27AB5@scorecrow.com \
--to=ntg@scorecrow.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).