unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Chris Marusich" <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Makefile logic to create Guix documentation
Date: Tue, 16 Jun 2020 17:02:17 +0200	[thread overview]
Message-ID: <86imfrqcjq.fsf@gmail.com> (raw)
In-Reply-To: <87eeqfwdp3.fsf@gnu.org>

Hi,

Speaking about Makefile and Guix documentation, I have remarked things
(maybe I am doing wrong) that annoys me time to time.

1. "make info" is not self consistent.

--8<---------------cut here---------------start------------->8---
./doc/guix.texi:11297: @include: could not find os-config-bare-bones.texi
./doc/guix.texi:11438: @include: could not find os-config-desktop.texi
./doc/guix.texi:11445: @include: could not find os-config-lightweight-desktop.texi
make[1]: *** [Makefile:4078: doc/guix.info] Error 1
--8<---------------cut here---------------end--------------->8---


2. I am always confused how to generate the EPS/PNG of "doc/images" and
   generally I end up with "make ... wait C-c".


3. The modified PO files under "po/{guix,packages}/" hangs Magit and
   then Emacs so generally I have to restore them before going back to
   Magit.
   

I am not enough annoyed to unwrap the logic of Makefile and propose a
patch but if someone is visiting the topic... Or maybe a tips for
improving my workflow. :-)


All the best,
simon


      reply	other threads:[~2020-06-16 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14  0:48 Makefile logic to create Guix documentation Chris Marusich
2020-06-14  3:12 ` Julien Lepiller
2020-06-14  5:08   ` Chris Marusich
2020-06-16  9:40 ` Ludovic Courtès
2020-06-16 15:02   ` zimoun [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=86imfrqcjq.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=cmmarusich@gmail.com \
    --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).