From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: beta vs current
Date: Fri, 31 Jan 2020 09:56:27 +1300 [thread overview]
Message-ID: <e2f3cf1e-9b10-7d67-9e84-8e2527d38cef@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.77.849.2001301436020.1885283@ervasbepr.pvz.zptvyy.pn>
On 1/31/20 8:37 AM, Aditya Mahajan wrote:
> On Thu, 30 Jan 2020, Hans Hagen wrote:
>
>> Hi,
>>
>> Already for quite some years the 'current' context release is the one
>> that ends up on texlive. The rest of the year we talk about betas and
>> very rarely an alpha release. This distinction no longer makes sense.
>>
>> From now on there will be no alpha, beta or current (with latest begin
>> the most recent of the three, when present): we only will have latest.
>> Most users follow the latest anyway and keeping a copy of some tree is
>> cheap.
>>
>> There will of course be the yearly tex live snapshots and these will
>> have the year attached to them.
>>
>> So, effectively nothing changes, apart from the fact that we no longer
>> use the labels (and distinction on the website).
>
> I like this change.
>
>> A more fundamental distinction is between the versions:
>>
>> pdftex|xetex : mkii (probaly not used that much any longer)
>> luatex|luajittex : mkiv (also the test for luatex dev)
>> luametatex : lmtx (the (upcoming) real deal)
>>
>> Mojca and I are diuscussing / working on an upgrade of the context
>> garden installations and repositories but more about that later,
>
> Will lmtx be available on the next texlive?
Probably not, LuaMetaTeX sources are not public yet, so TeX Live can't
build it and I don't think they are going to just pull binaries into the
tree. They are also very cautious with licensing, so unless something
is truly open source they won't pull it (e.g. https://ctan.org/pkg/pgf-pie).
Cheers, Henri
> Aditya
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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-01-30 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 13:18 Hans Hagen
2020-01-30 19:37 ` Aditya Mahajan
2020-01-30 20:56 ` Henri Menke [this message]
2020-01-30 21:56 ` 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=e2f3cf1e-9b10-7d67-9e84-8e2527d38cef@gmail.com \
--to=henrimenke@gmail.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).