ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to update LMTX?
Date: Thu, 4 Apr 2019 23:06:23 +0200	[thread overview]
Message-ID: <889cde18-79ef-d185-9e17-627f6194c88d@xs4all.nl> (raw)
In-Reply-To: <01cae495-fb23-956e-7d91-0cadf033d6d0@gmail.com>

On 4/4/2019 10:27 PM, Henri Menke wrote:
> Dear list,
> 
> With ConTeXt standalone there was an easy way to update the install script and
> the distrivution using
> 
>      rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .
>      sh ./first-setup.sh --context=latest --engine=luatex --modules=all --fonts=all
> 
> For LMTX it seems that I have to download the zip from
> http://www.pragma-ade.nl/install.htm, extract it and then run install.sh to

first=setup.sh never changed so there was no reason to download that, 
and the idea is that install.sh also is rather stable (and like 
fitst-setup it also updates)

> account for possibly updated installation scripts.  Is there a resource where I
> can download the (unzipped) install script and binaries via rsync directly?

currently not, you can just rerun the install script and it will only 
fetch new files (which is pretty fast) (unzipping the beta zip in 
texmf-context probably works ok too but that won't update binaries)

> On another note, it seems that I can't install modules and fonts in LMTX.  When running
> 
>      mtxrun --script mtx-install.lua --help
> 
> I can see the options --modules and --fonts but running

for modules and fonts you have to wait till mojca has the garden up and 
running (for now you can just copy the subtrees from a regular 
installation)

(i don't have such a local fonts tree as my own fonts tree is way larger 
and i don't want mixups)

>      bin/mtxrun --script ./bin/mtx-install.lua --update --server="..." --instance="..." --modules=all --fonts=all
> 
> seems to have no effect.  How do I install modules and fonts?
see above

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2019-04-04 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 20:27 Henri Menke
2019-04-04 20:32 ` Alan Braslau
2019-04-04 20:36   ` Henri Menke
2019-04-04 21:11     ` Hans Hagen
2019-04-04 22:09       ` Alan Braslau
2019-04-04 22:20         ` Hans Hagen
2019-04-04 21:06 ` Hans Hagen [this message]

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=889cde18-79ef-d185-9e17-627f6194c88d@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --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).