From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: New installation setup (was: Cannot build plain format)
Date: Sun, 19 Apr 2020 12:44:43 +0200 [thread overview]
Message-ID: <5983FBFF-3ABA-481E-B328-DC798BD26856@fiee.net> (raw)
In-Reply-To: <e09d92fa-7c34-56a8-9c41-9ab71c5fd606@xs4all.nl>
> Am 19.04.2020 um 11:57 schrieb Hans Hagen <j.hagen@xs4all.nl>:
> As a side note: a while ago mojca and i discussed the future repository and installation setup which will use github repositories
>
> (1) - context (including luametatex sources)
> (2) - binaries (for a subset of platforms)
> (3) - resources (like fonts and such)
> (4) - modules (stable ones pushed from the main garden repos)
>
> but we simply didn't find time to follow up on that. We have to adapt installers too and we want to do it right from the start.
>
> Now, we're not in a particular hurry, but in playing with all this it can happen that the current distributions get flaws.
>
> (As a side effect the more or less official release of luametatex has been postponed a few times because it depends on (1) which in turn depends on pushing older context distributions etc. But then, due to the current health crisis, time has slowed down anyway.)
Sounds good. Is documentation part of (3) or can it be another section?
While I want to install "everything" on my work machine, it would make sense to restrict a server installation (or a beta version for tests) to the bare minimum (without docs, but maybe with fonts).
I also would very much appreciate to be able to install older versions (like "in the old times") to check when some changes happened. Git repositories serve the same purpose, probably even better.
I’d suggest to keep those sections in separate repositories and install them as texmf-context, texmf-fonts, texmf-docs or the like (similar to the current state, but selectable). Git submodules *should* work to combine several repos, but the implementation has flaws (e.g. "git submodule update" tries to access all submodules at once, and if you must enter credentials, the prompts get mixed up).
Best, Hraban
___________________________________________________________________________________
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:[~2020-04-19 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:51 Cannot build plain format Henri Menke
2020-04-16 10:35 ` Hans Hagen
2020-04-16 23:51 ` Henri Menke
2020-04-19 9:57 ` Hans Hagen
2020-04-19 10:44 ` Henning Hraban Ramm [this message]
2020-04-19 13:39 ` New installation setup Hans Hagen
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=5983FBFF-3ABA-481E-B328-DC798BD26856@fiee.net \
--to=texml@fiee.net \
--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).