unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Program to build the on-line manuals (HTML + PDF)
Date: Mon, 20 May 2019 23:52:53 +0200	[thread overview]
Message-ID: <877eakiyiy.fsf@elephly.net> (raw)
In-Reply-To: <87ftp9v2st.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Here’s a build program I used to generate all the gnu.org/s/guix/manual
> hierarchy, with all the languages, HTML and PDF.
>
> You can drop in your Guix tree and run, say:
>
>   GUIX_MANUAL_VERSION=1.0.1 guix build -f build.scm
>
> to build the manual for 1.0.1.

Neat!

It seems that this must be run from the “doc” directory, because it
assumes that the git repository root is in the parent directory of the
current working directory.

I haven’t been able to successfully run it yet.  I’m on the master
branch and issued

    GUIX_MANUAL_VERSION=1.0.1 ../pre-inst-env guix build -f build.scm

from within the “doc” directory, but this is what I get:

--8<---------------cut here---------------start------------->8---
;;; (repo "/home/rekado/dev/gx/branches/master/doc/..")
guix build: error: failed to load 'build.scm':
git/branch.scm:101:8: Git error: cannot locate remote-tracking branch 'origin/version-1.0.1'
--8<---------------cut here---------------end--------------->8---

> Regarding PDFs, I failed to use something smaller than the big ‘texlive’
> package.  I’d very much welcome help in that area!

I’ll try to debug this and report back.

-- 
Ricardo

  reply	other threads:[~2019-05-20 22:09 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 [this message]
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

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=877eakiyiy.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).