all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Hwo to debug and teacking builds?
Date: Tue, 28 Mar 2017 23:10:46 -0700	[thread overview]
Message-ID: <87vaqsfw9l.fsf@gmail.com> (raw)
In-Reply-To: CAJ98PDxsF-hzozm6BsMNShM4pQYqOR=tSw6WQST5zpVaLJHBww@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]

Catonano <catonano@gmail.com> writes:

> This is important information and it's more detailed than what Pjotr wrote in his wrap up 
>
> I'd do it myself but I don't know the first thing about the info system
>
> Which is the source file ? 

I'm sure your contribution would be welcome!  The source is in guix/doc,
mostly in guix.texi.

> How do I compile it ?

Get the dependencies:

  guix environment guix --ad-hoc texlive

Make everything:

  make

Make just the documentation, in Info format:

  make info

If you're curious to understand why these targets exist, please refer to
the Automake manual for details:

https://www.gnu.org/software/automake/manual/automake.html#Documentation

After making changes to the guix.texi file, just re-run the 'make'
invocation, and it will quickly recompile just the documentation.

To view your changes, it's helpful to add the 'guix/doc' directory from
your local Guix checkout to your INFOPATH.  I've put the following line
in my ~/.bash_profile to do this automatically:

  export INFOPATH="$HOME/guix/doc${INFOPATH:+:}$INFOPATH"

That way, when you invoke 'guix info' (or 'C-h i' in Emacs), you'll see
the updated version.  I don't know how to preview changes in real-time
as you modify guix.texi, but if you learn how, please let me know!

> Which Emacs mode should I use ?

Try texinfo-mode (see: (texinfo) Emacs Editing).

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-03-29  6:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  9:16 Hwo to debug and teacking builds? Hartmut Goebel
2017-03-28  9:52 ` Ludovic Courtès
2017-03-28 13:45   ` Catonano
2017-03-28 16:07     ` ng0
2017-03-28 18:11       ` Catonano
2017-03-28 18:24         ` ng0
2017-04-10  6:39         ` Ricardo Wurmus
2017-04-10  7:19           ` Catonano
2017-03-29  6:10     ` Chris Marusich [this message]
2017-03-29 10:36       ` Catonano
2017-04-11 14:15       ` myglc2
2017-04-11 15:40         ` Chris Marusich
2017-04-11 16:36           ` Hartmut Goebel
2017-04-11 19:01             ` myglc2
2017-04-13  1:32             ` Chris Marusich
2017-03-28 15:58   ` Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vaqsfw9l.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=catonano@gmail.com \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.