From: "Hans Åberg" <haberg-1@telia.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Andrew Dunning <andrew.dunning@utoronto.ca>
Subject: Re: Homebrew packaging for macOS
Date: Sun, 7 Oct 2018 15:06:33 +0200 [thread overview]
Message-ID: <187CB251-6AA3-40A4-8F84-C8A99D0BA719@telia.com> (raw)
In-Reply-To: <eebf832f-e256-66e1-7849-50b58ca1deeb@xs4all.nl>
> On 7 Oct 2018, at 12:45, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> 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)
I don't recall the problem, maybe using LuaTeX in another context that ConTeXt, so having to keep track of that switch.
> (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)
I get weekly update update notices from the TeX Live Utility, so it seems working fine at that end.
___________________________________________________________________________________
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:[~2018-10-07 13:06 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
2018-10-07 13:06 ` Hans Åberg [this message]
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=187CB251-6AA3-40A4-8F84-C8A99D0BA719@telia.com \
--to=haberg-1@telia.com \
--cc=andrew.dunning@utoronto.ca \
--cc=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).