unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Manual structure
Date: Sat, 05 Mar 2016 23:17:21 -0500	[thread overview]
Message-ID: <87pov8fdf2.fsf@gmail.com> (raw)
In-Reply-To: 20160305154245.GA25307@solar

Andreas Enge <andreas@enge.fr> writes:
[...]
> Concretely, I suggest the following:
> - Rename "7.6 Packaging Guidelines" to "Packages", and move it one level up
>   between the current 6 and 7 as the new chapter 7. Somehow integrate 7.3 
>   to 7.8 here.
> - Move 7.1 and 7.2 to new chapters 8 and 9.
>
> What do you think?

Great idea. While you are at it, please consider additional changes to
reorganize sections by package management vs system configuration and
users vs coders, perhaps along the lines shown below. Current section
numbers in ()'s.

* GNU GUIX Ref Man

** intro (1)

** Using Guix package management (3.1)
*** Installation
**** from Binary (2.1)
**** from Source (2.2, 2.3, 2.4, 2.5)
*** Package Management
**** Application Setup (2.6)
**** Package Management (3, 7.4)

** Using Guix System Distribution (7)
*** Installation
**** By USB (7.1)
**** Converting Guix to GuixSD (TK)
*** System Configuration (7.2)

** Using Guix Commands (6, 7.2.13)

** Using the Guix in Emacs (4)

** Coding in Guix
*** Building from Git (8.1, 8.2, 8.3)
*** programming interface (5)
*** packaging guidelines (7.5, 7.6)
*** system configuration (7.7, 7.8)
*** submitting code (8.4, 8.5)
*** debugging (7.3)

** acknowledgements
** appendix
** concept index
** programming index
** glossary (TK)

  reply	other threads:[~2016-03-06  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05 15:42 Manual structure Andreas Enge
2016-03-06  4:17 ` myglc2 [this message]
2016-03-06 14:05 ` 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=87pov8fdf2.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=guix-devel@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).