ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: "Hans Åberg" <haberg-1@telia.com>,
	"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Andrew Dunning <andrew.dunning@utoronto.ca>
Subject: Re: Homebrew packaging for macOS
Date: Sun, 7 Oct 2018 12:45:51 +0200	[thread overview]
Message-ID: <eebf832f-e256-66e1-7849-50b58ca1deeb@xs4all.nl> (raw)
In-Reply-To: <E5453216-B858-4FDE-86B7-1F9C12811FFD@telia.com>

On 10/7/2018 10:56 AM, Hans Åberg wrote:
> 
>> On 7 Oct 2018, at 01:32, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
>> On 10/7/2018 1:24 AM, Andrew Dunning wrote:
>>> Dear list,
>>> Has anyone ever looked into packaging ConTeXt for Homebrew on macOS (see <https://brew.sh>)? Providing it as an installation option would make it far easier to obtain the latest version.
>>
>> How do you now update? It's just one recall to first-setup.sh
> 
> It would be better to put the development version in TeXLive as a separate package—on MacOS, it comes with the TeX Live Utility which gives update notifications frequently, once a week, but one can run it more frequently by hand. Just give it a different name than from the ordinary distribution, say context-<version>.
> 
> When I used the beta, it was difficult to switch with other TeX software. So this might be better.
hm, you can install context alongside texlive and just change the path 
as everything else is picked up from that (also a lightweight context 
distribution is normally faster than context in texlive)

(till now we only update context in telive once per year and i don't 
know if mojca pushes the latest context in there for the updating; till 
now often it went in sync with a luatex update)

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
___________________________________________________________________________________

  reply	other threads:[~2018-10-07 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 23:24 Andrew Dunning
2018-10-06 23:32 ` Hans Hagen
2018-10-06 23:39   ` Andrew Dunning
2018-10-07  9:32     ` Jan U. Hasecke
2018-10-07 10:47       ` Hans Hagen
2018-10-07  8:56   ` Hans Åberg
2018-10-07 10:45     ` Hans Hagen [this message]
2018-10-07 13:06       ` Hans Åberg
2018-10-07 17:08 ` Mojca Miklavec
2018-10-09 13:26   ` Hans Åberg

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=eebf832f-e256-66e1-7849-50b58ca1deeb@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=andrew.dunning@utoronto.ca \
    --cc=haberg-1@telia.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).