From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 26604@debbugs.gnu.org
Subject: bug#26604: documentation: pdf generation is broken
Date: Tue, 4 May 2021 13:28:51 +0200 [thread overview]
Message-ID: <CAJ3okZ1QNs8ZG=BdAmu_AdWiPGkPR=ATULh2A9Y6pC26vX3uUQ@mail.gmail.com> (raw)
In-Reply-To: <87zgxastl1.fsf@elephly.net>
Hi,
On Tue, 4 May 2021 at 12:04, Ricardo Wurmus <rekado@elephly.net> wrote:
> At least the first “wizard stuff” is merely a list of packages.
> There isn’t anything we can do to avoid the selection of packages,
> because that stuff is modular by design. We could have an
> arbitrary collection of Texlive packages, but I’m sure we can’t
> agree on any good set because what exactly is needed depends on
> the document.
[...]
> If the problem is in figuring out what Texlive packages to install
> for generating the Guix manual: we can either document that or add
> the required packages to the inputs.
I agree. Maybe via a manifest file?
> If you still get errors relating to fonts or font maps: this has
> been fixed on the “master” branch; the texlive-configuration
> profile hook didn’t update the font maps.
Cool! I have missed.
Well, let close this old bug. \o/
Cheers,
simon
next prev parent reply other threads:[~2021-05-04 11:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 11:09 bug#26604: documentation: pdf generation is broken ng0
2017-04-23 4:14 ` Chris Marusich
2017-04-23 16:15 ` ng0
2017-04-23 18:42 ` Chris Marusich
2017-05-05 18:53 ` Ludovic Courtès
2020-09-28 19:57 ` zimoun
2020-09-28 21:15 ` Andreas Enge
2020-10-16 10:13 ` Ludovic Courtès
2020-10-16 11:16 ` zimoun
2021-05-03 14:06 ` Ricardo Wurmus
2021-05-04 8:02 ` zimoun
2021-05-04 10:04 ` Ricardo Wurmus
2021-05-04 11:28 ` zimoun [this message]
2021-05-23 15:17 ` Marius Bakke
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='CAJ3okZ1QNs8ZG=BdAmu_AdWiPGkPR=ATULh2A9Y6pC26vX3uUQ@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=26604@debbugs.gnu.org \
--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).