From: Isaac van Bakel <isaac.vanbakel@inf.ethz.ch>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 67660@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>,
Andreas Enge <andreas@enge.fr>
Subject: [bug#67660] [PATCH] gnu: texlive-xiften: Readd need input propagation
Date: Thu, 7 Dec 2023 12:06:09 +0100 [thread overview]
Message-ID: <4ab29d4c-2876-9bdd-d880-a1f909cd8956@inf.ethz.ch> (raw)
In-Reply-To: <87sf4fm2o9.fsf@nicolasgoaziou.fr>
Hello,
On 2023/12/06 22:39, Nicolas Goaziou wrote:
> This is a limitation in TeX Live, not Guix's, package definitions. The
> dependency is not reported in their "texlive.tlpdb" file.
>
> Note there are hundreds of such issues. We cannot realistically fix them
> manually ; for example this change would need to be tested every time
> Guix TeX packages are updated.
Is there no way to declare that a package auto-generated from TeX Live
should be "patched" in some way (in this case, to include the
dependency)? I'm aware that Nix does something like this for their
various package sets. Perhaps this would be more sustainable than a
fully-manual process.
> I suggest to use collections of packages to avoid messing too much with
> individual dependencies, and possibly report those missing dependencies
> to the TeX Live project.
Unfortunately this particular package only appears in an unopinionated
collection in latexextra, which is very heavy for something that I have
to put in my manifest just to fix a dependency issue.
I'll look into getting the dependency registered on TL, but it's worth
noting that they also don't want the responsibility of dependency
tracking. They also don't recommend that package authors bother to put
dependency information in their packages.[0] I'm conscious that this is
a complex burden, but ideally *someone* would take it on so that the
software works.
Best,
Isaac
[0]: https://tug.org/texlive/pkgcontrib.html#deps
next prev parent reply other threads:[~2023-12-07 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 14:01 [bug#67660] [PATCH] gnu: texlive-xiften: Readd need input propagation Isaac van Bakel
2023-12-06 21:39 ` Nicolas Goaziou via Guix-patches via
2023-12-07 11:06 ` Isaac van Bakel [this message]
2023-12-07 11:52 ` Nicolas Goaziou via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ab29d4c-2876-9bdd-d880-a1f909cd8956@inf.ethz.ch \
--to=isaac.vanbakel@inf.ethz.ch \
--cc=67660@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=mail@nicolasgoaziou.fr \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).