From: John Darrington <john@darrington.wattle.id.au>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: 01/02: gnu: Add itpp.
Date: Mon, 20 Mar 2017 07:03:03 +0100 [thread overview]
Message-ID: <20170320060302.GB19992@jocasta.intra> (raw)
In-Reply-To: <878to1571s.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 2848 bytes --]
On Sun, Mar 19, 2017 at 04:46:07PM -0400, Mark H Weaver wrote:
john@darrington.wattle.id.au (John Darrington) writes:
> jmd pushed a commit to branch master
> in repository guix.
>
> commit a53d6719bc6b6b4afdc58e257ac712df316c8858
> Author: John Darrington <jmd@gnu.org>
> Date: Tue Mar 7 07:51:51 2017 +0100
>
> gnu: Add itpp.
>
> * gnu/packages/maths.scm (itpp): New variable.
> ---
> gnu/packages/maths.scm | 30 +++++++++++++++++++++++++++++-
> 1 file changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/maths.scm b/gnu/packages/maths.scm
> index adc8156..fe85983 100644
> --- a/gnu/packages/maths.scm
> +++ b/gnu/packages/maths.scm
> @@ -1,7 +1,7 @@
> ;;; GNU Guix --- Functional package management for GNU
> ;;; Copyright ?? 2013, 2014, 2015, 2016 Andreas Enge <andreas@enge.fr>
> ;;; Copyright ?? 2013 Nikita Karetnikov <nikita@karetnikov.org>
> -;;; Copyright ?? 2014, 2016 John Darrington <jmd@gnu.org>
> +;;; Copyright ?? 2014, 2016, 2017 John Darrington <jmd@gnu.org>
> ;;; Copyright ?? 2014, 2015, 2016 Eric Bavier <bavier@member.fsf.org>
> ;;; Copyright ?? 2014 Federico Beffa <beffa@fbengineering.ch>
> ;;; Copyright ?? 2014 Mathieu Lirzin <mathieu.lirzin@openmailbox.org>
> @@ -761,6 +761,34 @@ Swath).")
> HDF5 file is encoded according to the HDF File Format Specification.")
> (license (license:x11-style "file://COPYING"))))
>
> +(define-public itpp
> + (package
> + (name "itpp")
> + (version "4.3.1")
> + (source (origin
> + (method url-fetch)
> + (uri (string-append "mirror://sourceforge/itpp/itpp/"
> + version "/itpp-"
> + version ".tar.gz"))
> + (sha256
> + (base32
> + "14ddy2xnb6sgp4hiax9v5sv4pr4l4dd4ps76nfha3nrpr1ikhcqm"))))
Please be more careful with the indentation above.
Do you know - I've been looking carefully at the above for about a minute now, and
I cannot see anything wrong with the indentation. I'm not saying that there isn't
anything wrong - but I cannot see it despite close scrutiny. So I must ask myself:
can we not be a little less strict about indentation?
Anyway Rekado has made me aware of emacs-guix and of etc/indent-code.el so maybe I'll
set up a git hook to use that.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-03-20 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170318093207.31474.12254@vcs0.savannah.gnu.org>
[not found] ` <20170318093208.C125820945@vcs0.savannah.gnu.org>
2017-03-19 20:46 ` 01/02: gnu: Add itpp Mark H Weaver
2017-03-20 6:03 ` John Darrington [this message]
2017-03-20 6:18 ` Leo Famulari
2017-03-20 6:38 ` John Darrington
2017-03-20 11:05 ` Alex Kost
2017-03-20 12:17 ` John Darrington
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=20170320060302.GB19992@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=mhw@netris.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).