From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add hdf-eos2.
Date: Wed, 19 Oct 2016 17:08:32 +0200 [thread overview]
Message-ID: <87inso74wf.fsf@gnu.org> (raw)
In-Reply-To: <20161013.111256.2080367666653045286.post@thomasdanckaert.be> (Thomas Danckaert's message of "Thu, 13 Oct 2016 11:12:56 +0200 (CEST)")
Hi!
Thomas Danckaert <post@thomasdanckaert.be> skribis:
> this patch adds HDF-EOS2 (which, somewhat confusingly, is completely
> independent from HDF-EOS5).
>
> I'm not sure what the best version name is. The tarball is
> HDF-EOS2.19v1.00.tar.Z, but documentation sometimes refers to it as
> “version 2.19”. The 2 is part of the library name, though, so I went
> with (version "19.1.0") in the end :-). Is there a policy for version
> labeling in Guix, and would (version "19v1.00") be ok?
There’s no policy for weird cases like this. :-) I personally prefer
“19.1.0”.
> From 53f69f5b4f0931b259ddd41ef25fc88a2ec6c26a Mon Sep 17 00:00:00 2001
> From: Thomas Danckaert <thomas.danckaert@gmail.com>
> Date: Fri, 30 Sep 2016 09:59:08 +0200
> Subject: [PATCH] gnu: Add hdf-eos2.
>
> * gnu/packages/maths.scm (hdf-eos2): New variable.
> * gnu/packages/patches/hdf-eos2-build-shared.patch: New file.
> * gnu/packages/patches/hdf-eos2-remove-gctp.patch: New file.
> * gnu/packages/patches/hdf-eos2-fortrantests.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add patches.
> + (synopsis "HDF4-based data format for NASA's Earth Observing System")
> + (description "HDF-EOS2 is a software library built on HDF4 which supports
> +the construction of data structures used in NASA's Earth Observing
> +system (Grid, Point and Swath).")
^
Capital S?
> --- /dev/null
> +++ b/gnu/packages/patches/hdf-eos2-build-shared.patch
> @@ -0,0 +1,23 @@
Please add a comment at the beginning of this patch.
> --- /dev/null
> +++ b/gnu/packages/patches/hdf-eos2-fortrantests.patch
> @@ -0,0 +1,329 @@
> +Fix multi-line string formatting in fortran test programs (reported upstream).
If there’s a URL for the bug report or upstream commit, could you add it
here?
The rest LGTM.
Could you send an updated patch?
Thanks!
Ludo’.
next prev parent reply other threads:[~2016-10-19 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 9:12 [PATCH] gnu: Add hdf-eos2 Thomas Danckaert
2016-10-19 15:08 ` Ludovic Courtès [this message]
2016-10-20 17:48 ` Thomas Danckaert
2016-10-24 21:10 ` 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=87inso74wf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/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.