From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: TeX Live 2014
Date: Mon, 07 Jul 2014 21:45:00 -0000 [thread overview]
Message-ID: <53BB14E1.1080409@cornell.edu> (raw)
In-Reply-To: <53B9A380.9020409@gmail.com>
On 7/6/2014 3:29 PM, Marco Atzeri wrote:
>
>
> On 04/07/2014 03:34, Ken Brown wrote:
>> On 7/3/2014 4:49 PM, Marco Atzeri wrote:
>>> On 02/07/2014 01:16, Ken Brown wrote:
>>>> Cygwin's TeX Live packages have been updated to the latest upstream
>>>> release, TeX Live 2014.
>>>
>>> Question:
>>> is python3 really a requirement ?
>>
>> I relied on cygport for the requirements, and it found python3 as a
>> requirement for seven of the collections. I've taken a quick look at a
>> couple of them, and I suspect that python3 shouldn't really be required.
>> But I'm not sure it's worth the trouble to go carefully through all
>> seven to be sure.
>>
>> Ken
>
> I suggest to review the requirements
> currently on cygwin64 texlive is pulling both python and python3
All of the python3 requirements are bogus, and I'll remove them. But
TeX Live contains many python scripts, so certainly some of the packages
should and do require python.
> I have strong doubts about both, and I do't see why texlive
> should require numpy
See /usr/share/texmf-dist/scripts/pgfplots/pgfplots.py (from
texlive-collection-pictures).
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2014-07-07 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 23:46 Ken Brown
2014-07-03 20:50 ` Marco Atzeri
2014-07-04 1:34 ` Ken Brown
2014-07-06 19:29 ` Marco Atzeri
2014-07-07 21:45 ` Ken Brown [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=53BB14E1.1080409@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@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).