On 2021-08-24 08:57, Ken Brown via Cygwin-apps wrote:
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.
With those fixed dependencies, I realise docbook-utils under scallywag
will pull in a lot of texlive collections, so I'll remove some
collections locally to check dependencies on underlying packages, rerun
zp_texlive_prep and zp_texlive_finish to ensure those still work, and
retry the build.
Specifiying explicit dependencies could possibly avoid this situation,
or at least provide pointers to the source of issues, in the future, if
texlive packaging and dependencies change again, improve robustness of
the build, provide documentation of that, and "for avoidance of doubt".
For example, as well as the component dependencies mentioned earlier,
docbook-utils cygport explicitly requires grep, perl, sed, despite those
currently being cygport dependencies, not mentioned in the docbook-utils
docs, and a perl module being required; all but perl are also currently
Base packages; similarly cygport explicitly requires those and other
Base packages, many script packages explicitly require bash, and other
packages explicitly require cygwin, although they are Base and essential
to everything.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
