From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Ken Brown <kbrown@cornell.edu>
Subject: Re: Scallywag TeX dblatex font requirements dependencies missing
Date: Sat, 8 Oct 2022 14:04:23 +0100 [thread overview]
Message-ID: <d5b4ae6a-01c0-7df5-1541-4367e33a26c5@dronecode.org.uk> (raw)
In-Reply-To: <65a59dea-123f-b574-6f84-eb56e0624703@SystematicSw.ab.ca>
On 30/09/2022 19:25, Brian Inglis wrote:
> On 2022-09-30 07:01, Jon Turney wrote:
>> On 29/09/2022 07:22, Brian Inglis wrote:
>>> Hi folks, [Please Reply All as Cygwin mail blocked by ISP]
>>>
>>> Scallywag job failing complaining about TeX fonts.
>>> Any ideas about what extra TeX font dependencies dblatex requires
>>> under gtk-doc building docs for gsasl 2.2 under playground:
>>>
>>> https://cygwin.com/cgi-bin2/jobs.cgi?id=4618
>>>
>>> https://github.com/cygwin/scallywag/actions/runs/3148865611/jobs/5119913953
>
>> Googling the first error message leads me to suggest
>> texlive-collection-fontsrecommended
>
> Thanks Jon,
>
> I planned to add that and ...extra, but shouldn't presumably required
> fonts be TeX/LaTex/dblatex package dependencies, when not mentioned
> anywhere in downstream packages, including in build scripts on other
> systems?
>
> How are maintainers and users expected to make the connection, if nobody
> mentions you need special "unrelated" font packages, in any of the
> downstream packages?
>
> For example, for DbLaTeX, only the Windows install page mentions MikTeX
> fonts, and there appears to be no other link between the abstract font
> specs, the TeX fonts used, and packages required, although there appear
> to be mentions of DejaVu "system" fonts, so do non-TeX font packages
> also need installed e.g. dejavu-fonts or urw-base35-fonts{,-legacy}?
>
> Those who are not TeXies need a few more hints.
I don't know.
Maybe Ken has some insight?
next prev parent reply other threads:[~2022-10-08 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 6:22 Brian Inglis
2022-09-30 13:01 ` Jon Turney
2022-09-30 18:25 ` Brian Inglis
2022-10-08 13:04 ` Jon Turney [this message]
2022-10-08 16:50 ` Ken Brown
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=d5b4ae6a-01c0-7df5-1541-4367e33a26c5@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=kbrown@cornell.edu \
/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).