From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: guix package / output for guix documentation
Date: Wed, 3 May 2017 12:33:43 +0000 [thread overview]
Message-ID: <20170503123343.3bet233kmrlxyuzs@abyayala> (raw)
Do you think it could be good to provide the output of
guix' "make doc/guix.html" and other make doc/ outputs
in a separate package (or outputs of guix itself)?
My idea is to have an independent online/offline version
of the html documentation, matching some snapshot or
commit id.
In my case, I will provide this online, currently solved
with a script instead of a guix package.
--
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/
next reply other threads:[~2017-05-03 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 12:33 ng0 [this message]
2017-05-03 12:54 ` guix package / output for guix documentation ng0
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=20170503123343.3bet233kmrlxyuzs@abyayala \
--to=contact.ng0@cryptolab.net \
--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).