On Fri, 2 Jul 2021, Jan U. Hasecke wrote:
>
> Dear Hans,
>
> thanks for the hint to the repo. I remember that it was mentiooned before.
>
> Am 02.07.21 um 10:42 schrieb Hans Hagen:
> > official : https://bitbucket.org/phg/context-mirror/src/beta/
There is also
github:
Dear Hans,
thanks for the hint to the repo. I remember that it was mentiooned before.
Am 02.07.21 um 10:42 schrieb Hans Hagen:
official : https://bitbucket.org/phg/context-mirror/src/beta/
Is there a how-to-bootstrap-from-repository? How can I get a running
context with the repo?
TIA
On 7/2/2021 11:56 AM, Jan U. Hasecke wrote:
Dear Hans,
thanks for the hint to the repo. I remember that it was mentiooned before.
Am 02.07.21 um 10:42 schrieb Hans Hagen:
official : https://bitbucket.org/phg/context-mirror/src/beta/
Is there a how-to-bootstrap-from-repository? How can I
On 7/2/2021 9:38 AM, Jan U. Hasecke wrote:
Am 02.07.21 um 01:07 schrieb Bruce Horrocks:
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
asecke
> Gesendet: Donnerstag, 1. Juli 2021 08:03
> An: mailing list for ConTeXt users
> Betreff: [NTG-context] Rolling out a pandoc-context publication workflow in an
> organization
>
>
> Dear all,
>
> in the last weeks I asked more questions than I normally do. The re
Am 02.07.21 um 01:07 schrieb Bruce Horrocks:
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"
On 1 Jul 2021, at 07:02, Jan U. Hasecke 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
Hi Taco,
thanks for this hint.
Am 01.07.21 um 08:44 schrieb Taco Hoekwater:
I would put the whole context distribution in the git. That way, you can
potentially hotfix something centrally.
Would you put texmf-cache into .gitignore?
Or is the cache portable to other machines?
juh
> On 1 Jul 2021, at 13:31, Jan U. Hasecke wrote:
>
> Hi Taco,
>
> thanks for this hint.
>
> Am 01.07.21 um 08:44 schrieb Taco Hoekwater:
>> I would put the whole context distribution in the git. That way, you can
>> potentially hotfix something centrally.
>
> Would you put texmf-cache into
On Thu, 1 Jul 2021, Taco Hoekwater wrote:
> Hi,
>
> > On 1 Jul 2021, at 08:02, Jan U. Hasecke wrote:
> >
> > I come up with the idea of an "organizational context distribution" that
> > has all requirements preinstalled. That could look like this:
>
> I would put the whole context
Dear all,
in the last weeks I asked more questions than I normally do. The reason
is that my organization is discussing to roll out a
markdown-pandoc-context publication workflow.
Some time ago we started to use context to produce flyers and some other
documents. In fact I was the only one
Hi,
> On 1 Jul 2021, at 08:02, Jan U. Hasecke wrote:
>
> I come up with the idea of an "organizational context distribution" that has
> all requirements preinstalled. That could look like this:
I would put the whole context distribution in the git. That way, you can
potentially hotfix
12 matches
Mail list logo