From: "Daniel Meißner via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 65889@debbugs.gnu.org
Subject: bug#65889: texlive-acronyms is missing dependencies
Date: Wed, 13 Sep 2023 23:21:38 +0200 [thread overview]
Message-ID: <87sf7h93bx.fsf@ruhr-uni-bochum.de> (raw)
In-Reply-To: <87zg1qth8f.fsf@nicolasgoaziou.fr>
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Daniel Meißner via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
>
[...]
>> I can provide a patch if desired to add texlive-xstring and
>> texlive-bigfoot to texlive-acronym’s (propagated-)inputs. The suffix
>> package appears to be bundled with texlive-bigfoot. Do we want to
>> unbundle it or simply add texlive-bigfoot to the (propagated-)inputs?
>
> We use dependencies specified in TeX Live itself (as in "texlive.tlpdb"
> file), for sanity reasons. There are 4000+ packages; I think it is not
> reasonable to grep through their output to find the unspecified
> dependencies. It will also be terrible when using some updater, now this
> tool can remove propagated inputs.
>
> Most dependencies issues are resolved installing collections of
> packages, such as `texlive-collection-latexrecommended'. As a data
> point, I only resolve dependencies "manually" when they would otherwise
> require me to install `texlive-collection-latexextra', which is just too
> big.
>
> AFAIC, I suggest to not fix this, as this is not worth the trouble.
I see, makes sense. I am closing this issues then. Thanks for your
fast reply and your hint to use collections instead. I sometimes make a
game out of the most minimal Texlive manifest.scm for my TeX writings :D
Best
--
Daniel
next prev parent reply other threads:[~2023-09-13 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 9:15 bug#65889: texlive-acronyms is missing dependencies Daniel Meißner via Bug reports for GNU Guix
2023-09-13 12:01 ` Nicolas Goaziou
2023-09-13 21:21 ` Daniel Meißner via Bug reports for GNU Guix [this message]
2023-09-14 13:12 ` Josselin Poiret via Bug reports for GNU Guix
2023-09-14 13:13 ` Josselin Poiret via Bug reports for GNU Guix
2023-09-14 16:53 ` Nicolas Goaziou
2023-10-01 16:01 ` Bruno Victal
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=87sf7h93bx.fsf@ruhr-uni-bochum.de \
--to=bug-guix@gnu.org \
--cc=65889@debbugs.gnu.org \
--cc=daniel.meissner-i4k@rub.de \
--cc=mail@nicolasgoaziou.fr \
/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).