From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Program to build the on-line manuals (HTML + PDF)
Date: Thu, 11 Jul 2019 17:46:40 +0200 [thread overview]
Message-ID: <87ef2wtvz3.fsf@gnu.org> (raw)
In-Reply-To: <87k1csjmyb.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 08 Jul 2019 22:22:36 +0200")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
>> I’ve committed an improved version of doc/build.scm as
>> ccadafdcefee012c261513e9d8663a22704bc496.
>>
>> It expects to be used from a Git checkout like so:
>>
>> guix build -f doc/build.scm
>>
>> Hopefully it addresses the issues you had before, Ricardo.
>
> It does! It’s really great. I just updated guix.gnu.org with this
> command:
>
> GUIX_WEB_SITE_URL="//guix.gnu.org/" ./pre-inst-env guix build -f doc/build.scm
>
> And then
>
> rsync -rzvha --copy-links /gnu/store/…-guix-manual/ …/manual/
Neat!
>> There are a few FIXMEs in there (one is about TeX, as we discussed on
>> IRC last Friday) but it does the job.
>
> I see why you needed help with the modular TeX now… I started the
> wip-texlive branch to overhaul our TeX packages, but as it requires
> changes to svn-fetch and some core texlive-* packages it will need to be
> merged into core-updates at some point.
That sounds good, I’m really happy there’s a way forward.
What’s currently the most difficult for me is to find out which packages
I should add to the union to do the task at hand, but once I’ve found
out, it’s really nice. :-)
Thank you,
Ludo’.
prev parent reply other threads:[~2019-07-11 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 10:27 Program to build the on-line manuals (HTML + PDF) Ludovic Courtès
2019-05-20 21:52 ` Ricardo Wurmus
2019-05-21 5:58 ` pelzflorian (Florian Pelz)
2019-05-21 7:14 ` Ricardo Wurmus
2019-05-21 11:24 ` Ricardo Wurmus
2019-07-07 15:37 ` Ludovic Courtès
2019-07-08 20:22 ` Ricardo Wurmus
2019-07-11 15:46 ` Ludovic Courtès [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=87ef2wtvz3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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).