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: scallywag zp_texlive_finish.dash failing exit code 2 rebuilding installed formats
Date: Tue, 24 Aug 2021 10:57:48 -0400	[thread overview]
Message-ID: <2008d2c6-64e0-c775-a911-d4431ee94009@cornell.edu> (raw)
In-Reply-To: <d88c5abe-b47f-2d42-70de-b5065bb297dc@SystematicSw.ab.ca>

On 8/23/2021 8:26 PM, Brian Inglis wrote:
> On 2021-08-23 15:08, Ken Brown via Cygwin-apps wrote:
>> On 8/23/2021 2:46 PM, Brian Inglis wrote:
>>> On 2021-08-22 16:58, Ken Brown via Cygwin-apps wrote:
>>>> OK, your later messages explain it better.  I'll have to look at 
>>>> texlive-collection-formatsextra; it's possible that it needs to require 
>>>> texlive-collection-fontsrecommended.  But a better solution to your 
>>>> immediate problem would be for someone to look at docbook-utils and see 
>>>> whether it really needs texlive-collection-formatsextra.  It currently 
>>>> requires the obsolete texlive-collection-htmlxml, which pulls in a lot of 
>>>> other packages, probably unnecessarily in most cases.  See
>>>>    https://cygwin.com/packages/summary/texlive-collection-htmlxml.html
> 
>>> That would require a TeX-y who knows the TeX relationships of the files.
>>>  From what I can see jadetex and pdfjadtex are used by docbook-utils,
> 
>> OK, so docbook-utils definitely needs texlive-collection-formatsextra, which 
>> is what I hoped to avoid.  In that case, it's probably not worth checking 
>> whether it needs the other dependencies of texlive-collection-htmlxml.
>> And jadetex needs texlive-collection-fontsrecommended for marvosym, so I need 
>> to fix the dependencies of texlive-collection-formatsextra.  I'll do that 
>> shortly.
> 
> Thanks Ken
> 
>> Thanks for reporting the problem.
> 
> I will trim back the BUILD_REQUIRES to ...formatsextra (and ...plaingeneric? for 
> html?) without other additions to see if zp_texlive_finish.dash completes under 
> scallywag and also whether the package builds with just those packages.

Why do you need explicit texlive build dependencies at all?  If what you really 
need is docbook-utils, you should just require it and let it pull in whatever 
texlive collections are needed.  This should work now that I've fixed formatsextra.

Ken

  reply	other threads:[~2021-08-24 14:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22  0:48 Brian Inglis
2021-08-22 15:15 ` Jon Turney
2021-08-22 15:33   ` Brian Inglis
2021-08-22 21:57     ` Brian Inglis
2021-08-22 22:38       ` Ken Brown
2021-08-22 22:58         ` Ken Brown
2021-08-23 18:46           ` Brian Inglis
2021-08-23 21:08             ` Ken Brown
2021-08-24  0:26               ` Brian Inglis
2021-08-24 14:57                 ` Ken Brown [this message]
2021-08-24 17:17                   ` Brian Inglis
2021-08-22 22:20     ` /etc/postinstall/zp_texlive_finish.dash fails missing marvosysm.sty Brian Inglis
2021-08-22 22:26     ` Brian Inglis
2021-08-22 15:21 ` scallywag zp_texlive_finish.dash failing exit code 2 rebuilding installed formats Brian Inglis

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=2008d2c6-64e0-c775-a911-d4431ee94009@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).