From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: ConTeXt no longer available on Cygwin
Date: Thu, 13 Apr 2023 18:25:06 -0400 [thread overview]
Message-ID: <ac25455e-0e29-80e9-bc5e-65dc793058fc@cornell.edu> (raw)
In-Reply-To: <10526155-845f-ba90-6711-56b302287b7c@cornell.edu>
[This is a follow-up to
https://cygwin.com/pipermail/cygwin/2023-March/253326.html, on the
cygwin list.]
On 3/24/2023 11:00 AM, Ken Brown via Cygwin wrote:
> On 3/22/2023 12:56 PM, Ken Brown via Cygwin wrote:
>> As I mentioned in the announcement of TeX Live 2023, there has been a
>> major change in ConTeXt; see
>>
>> https://tug.org/texlive/bugs.html
>>
>> Briefly, ConTeXt development has been moved out of TeX Live into a
>> separate project. Unfortunately, the maintainer of that project
>> decided to remove Cygwin support, so I cannot easily provide a context
>> binary. One Cygwin user of ConTeXt complained upstream, to no avail.
>>
>> At some point I will probably remove the texlive-collection-context
>> package, which is now useless. But I am waiting to see how other
>> distros are going to deal with this change.
>>
>> If you will be greatly inconvenienced by the absence of a context
>> binary, please let me know by replying to this message. There may or
>> may not be anything I can do about it.
>
> This turned out to be simple to fix. I will do that shortly, but first
> I want to finish discussing this with TeX Live maintainers for other
> distros.
This turns out to be a complete mess, with no uniformity among
maintainers, so I'm on my own. The simplest way for me to handle it is
to package the missing binary as part of texlive-collection-context.(*)
This presumably means that the latter can no longer be a noarch package.
Jon, can you (or calm) cope with a package changing from noarch to
x86_64? Alternatively, I could make a completely new package, say
texlive-context-bin, which contains only the binary, if you think that's
better.
Ken
(*) It used to be contained in the texlive package, but the sources are
no longer in the texlive source tree, and the build system is completely
different.
next parent reply other threads:[~2023-04-13 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <feca8f1d-f1da-8b76-e9e9-9218e648c9d6@cornell.edu>
[not found] ` <10526155-845f-ba90-6711-56b302287b7c@cornell.edu>
2023-04-13 22:25 ` Ken Brown [this message]
2023-04-14 9:13 ` Marco Atzeri
2023-04-14 10:14 ` Jon Turney
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=ac25455e-0e29-80e9-bc5e-65dc793058fc@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).