public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [attn maintainer] latex dependencies
Date: Thu, 14 Dec 2023 17:21:32 -0500	[thread overview]
Message-ID: <62dff8be-dca0-4827-9c78-00235b82feb3@cornell.edu> (raw)
In-Reply-To: <56409e17-969f-47f8-bfcc-599cc65b0585@gmail.com>

On 12/14/2023 2:46 PM, Marco Atzeri via Cygwin-apps wrote:
> On 14/12/2023 16:50, Ken Brown via Cygwin-apps wrote:
>> On 12/14/2023 4:22 AM, Marco Atzeri via Cygwin-apps wrote:
>>> Hi Ken,
>>>
>>> it seems that both
>>>
>>>     texlive-collection-latex
>>>     texlive-collection-latexextra
>>>
>>> depend on
>>>
>>>    texlive-collection-latexrecommended
>>>
>>> that seems to me contra intuitive. can you please check ?
>>
>> Hi Marco,
>>
>> Do you have an example of a LaTeX file that uses packages only in 
>> texlive-collection-latex but fails to compile if 
>> texlive-collection-latexrecommended is not installed?  Without this, 
>> it's very hard for me to check if the occurrences of "pdftexcmds.sty" 
>> that you found really indicate dependencies.  My technical knowledge 
>> of LaTeX is not good enough to determine this just from looking at the 
>> .sty files.  See below for further comments on a few of the occurrences.
>>
> 
> the last gl2ps package had such issue
> 
> https://github.com/cygwin/scallywag/actions/runs/7204747329/job/19626758626
> 
> adding the texlive-collection-latexrecommended
> as dependency, solved that issue
> 
> https://github.com/cygwin/scallywag/actions/runs/7206881393/job/19632744288

Thanks.  The problem is that line 111 of 
/usr/share/texmf-dist/tex/latex/hyperref/hyperref.sty contains 
\RequirePackage{pdftexcmds}.  Since hyperref is in the latex collection, 
pdftexcmds should also be in that collection.  I'll report this upstream.

But there's no bug in the latexextra package.  The upstream latexextra 
collection does indeed depend on the latexrecommended collection, and 
this is reflected in the Cygwin packaging.  So this dependency is by 
design (and it makes intuitive sense to me).

Thanks for the report.

Ken

  reply	other threads:[~2023-12-14 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  9:22 Marco Atzeri
2023-12-14 15:50 ` Ken Brown
2023-12-14 19:46   ` Marco Atzeri
2023-12-14 22:21     ` Ken Brown [this message]
2023-12-15  2:28       ` Marco Atzeri

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=62dff8be-dca0-4827-9c78-00235b82feb3@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).