From: Bruno Victal <mirai@makinata.eu>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: daniel.meissner-i4k@rub.de, 65889@debbugs.gnu.org,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: bug#65889: texlive-acronyms is missing dependencies
Date: Sun, 1 Oct 2023 17:01:44 +0100 [thread overview]
Message-ID: <71690a2f-e560-4b2d-a57c-7ffb61cca148@makinata.eu> (raw)
In-Reply-To: <87wmws3nk1.fsf@jpoiret.xyz>
Hi Josselin,
On 2023-09-14 14:13, Josselin Poiret via Bug reports for GNU Guix wrote:
> Couldn't we report those missing dependencies upstream then?
This can be done, in theory it's nothing too complicated and all it takes
is simply add a DEPENDS.txt file to the repository.
If you're interested in doing this, see [1] and [2] for information.
As Nicolas has pointed out, it's untenable to do an exhaustive listing of
the dependencies so I'd recommend installing some typical collections first
such as `texlive-collection-latexrecommended' and only then report the
missing non-obvious dependencies for inclusion in a DEPENDS.txt to upstream.
[1]: <https://tex.stackexchange.com/a/598696>
[2]: <https://www.tug.org/texlive/pkgcontrib.html#deps>
--
Furthermore, I consider that nonfree software must be eradicated.
Cheers,
Bruno.
prev parent reply other threads:[~2023-10-01 16:12 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
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 [this message]
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=71690a2f-e560-4b2d-a57c-7ffb61cca148@makinata.eu \
--to=mirai@makinata.eu \
--cc=65889@debbugs.gnu.org \
--cc=daniel.meissner-i4k@rub.de \
--cc=dev@jpoiret.xyz \
--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).