From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add gnu-maintain and gnu-standards.
Date: Fri, 25 Mar 2016 11:18:20 +0100 [thread overview]
Message-ID: <87fuvesvwz.fsf@gnu.org> (raw)
In-Reply-To: <87a8lokhs3.fsf@drakenvlieg.flower> (Jan Nieuwenhuizen's message of "Wed, 23 Mar 2016 22:26:20 +0100")
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> From 914756aa6c8893ce68f57dab575ed67f4d5ae560 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke@gnu.org>
> Date: Wed, 23 Mar 2016 22:18:46 +0100
> Subject: [PATCH] gnu: Add gnu-maintain and gnu-standards.
>
> * gnu/packages/gnu-doc.scm: New file.
Please add it to gnu-system.am as well.
The ‘miscfiles’ package should probably go to the same module (in a
separate commit.)
> + (source (origin
> + (method url-fetch)
> + (uri "http://www.gnu.org/prep/maintain/maintain.texi.tar.gz")
This is an unversioned URL where the file occasionally gets updated in
place, so it’s unsuitable.
I think this one should instead be taken from
:pserver:anonymous@cvs.savannah.gnu.org:/sources/gnustandards using
(guix cvs-download).
> +(define-public gnu-standards
> + (package
> + (name "gnu-standards")
> + (version "2015-04-23")
> + (source (origin
> + (method url-fetch)
> + (uri "http://www.gnu.org/prep/standards/standards.texi.tar.gz")
> + (sha256
> + (base32
> + "1rdyqk6d5bgrpmlnb8r65qif1h604jz1g7v3szh24cqga3mgi9py"))))
Likewise.
> + (description "The GNU Coding Standards were written by Richard Stallman and other GNU Project volunteers. Their purpose is to make the GNU system clean, consistent, and easy to install.")
Please shrink the line, as suggested by ‘guix lint’.
Could you send an updated patch?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-03-25 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 21:26 [PATCH] gnu: Add gnu-maintain and gnu-standards Jan Nieuwenhuizen
2016-03-25 10:18 ` Ludovic Courtès [this message]
2016-03-26 13:00 ` Jan Nieuwenhuizen
2016-03-31 21:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuvesvwz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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.