From: Eric Bavier <ericbavier@openmailbox.org>
To: Jeremy Robst <jpro@bas.ac.uk>
Cc: guix-devel@gnu.org,
Guix-devel
<guix-devel-bounces+ericbavier=openmailbox.org@gnu.org>
Subject: Re: [PATCH] gnu: Add hdf4
Date: Tue, 24 May 2016 14:06:17 -0500 [thread overview]
Message-ID: <eb7b24f7912f3027cf3a0103e898745d@openmailbox.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1605241414480.16068@jpro.nerc-bas.ac.uk>
On 2016-05-24 08:20, Jeremy Robst wrote:
> Hi,
>
> I could apply the previous patch, but I've created a new one (below)
> that handles the tests (I think).
>
>>> + (license (license:x11-style
>>> +
>>> "https://www.hdfgroup.org/ftp/HDF/HDF_Current/src/unpacked/COPYING"))))
>>
>> To me, this looks more like a variation on the BSD license than the
>> x11
>> license. Perhaps non-copyleft is a more appropriate choice. Can you
>> look
>> at some of our packages using non-copyleft and report back?
>
> I've changed the license to non-copyleft, which I think is closer. I
> was copying the hdf5 license definition, which is very similar and
> probably should also be changed.
Indeed.
> The definition for hdf4 still isn't quite right though, it doesn't
> generate a reproducible build - the hdf4 configure script generates a
> file lib/libhdf4.settings (from libhdf4.settings.in) which includes
> the config time, user, system information, which obviously changes
> from build to build or system to system.
>
> What's the best way to resolve this ?
Could we apply a variation of the hdf5-config-date.patch?
> --
> jpro@bas.ac.uk | (work) 01223 221402 (fax) 01223 362616
> Unix System Administrator - British Antarctic Survey
> #include <disclaimer.std>
>
> From 857fb05c7dcc8f19dc7d4cf04039743137f4f0ae Mon Sep 17 00:00:00 2001
> From: Jeremy Robst <jpro@bas.ac.uk>
> Date: Mon, 23 May 2016 17:59:00 +0100
> Subject: [PATCH] gnu: Add hdf4
>
> * gnu/packages/maths.scm (hdf4): New variable
> ---
> gnu/packages/maths.scm | 43
> +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 43 insertions(+)
>
> diff --git a/gnu/packages/maths.scm b/gnu/packages/maths.scm
> index 19ed44f..00c0310 100644
> --- a/gnu/packages/maths.scm
> +++ b/gnu/packages/maths.scm
> @@ -408,6 +408,49 @@ plotting engine by third-party applications like
> Octave.")
> (license (license:fsf-free
>
> "http://gnuplot.cvs.sourceforge.net/gnuplot/gnuplot/Copyright"))))
>
> +(define-public hdf4
> + (package
> + (name "hdf4")
> + (version "4.2.11")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append
> + "http://www.hdfgroup.org/ftp/HDF/HDF_Current/src/hdf-"
> + version
> + ".tar.bz2"))
> + (sha256
> + (base32
> + "16yr50j845zlfx20skmw3y75ww77akk9gg0affjqkg66ih5r03mv"))))
> + (build-system gnu-build-system)
> + (native-inputs
> + `(("gfortran" ,gfortran)
> + ("bison" ,bison)
> + ("flex" ,flex)))
> + (inputs
> + `(("zlib" ,zlib)
> + ("libjpeg" ,libjpeg)))
> + (arguments
> + `(#:phases
> + (modify-phases %standard-phases
> + (add-before 'configure 'patch-configure
> + (lambda _
> + (substitute* '("mfhdf/hdfimport/testutil.sh.in"
> "hdf/util/testutil.sh.in")
> + (("/bin/rm") "rm")
> + (("/bin/mkdir") "mkdir"))
> + #t)))))
> +
> + (home-page "https://www.hdfgroup.org/products/hdf4/")
The blank line between these fields is not necessary.
> + (synopsis
> + "Library and multi-object file format for storing and managing
> data.")
> + (description "At its lowest level, HDF is a physical file format
> for
> +storing scientific data. At its highest level, HDF is a collection of
> +utilities and applications for manipulating, viewing, and analyzing
> data
> +in HDF files. Between these levels, HDF is a software library that
> provides
> +high-level APIs and a low-level data interface. ")
This description is noticeably more verbose than that of the hdf5
package. It seems like the first two sentences are not necessary here.
It would also be nice to summarize how hdf4 differs from hdf5.
--
`~Eric
next prev parent reply other threads:[~2016-05-24 19:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 17:22 [PATCH] gnu: Add hdf4 Jeremy Robst
2016-05-23 18:17 ` Leo Famulari
2016-05-24 13:20 ` Jeremy Robst
2016-05-24 19:06 ` Eric Bavier [this message]
2016-05-25 17:42 ` Jeremy Robst
2016-05-27 17:19 ` Leo Famulari
2016-05-28 14:32 ` Ludovic Courtès
2016-05-29 17:36 ` Jeremy Robst
2016-05-29 22:07 ` Ludovic Courtès
2016-06-02 14:43 ` Eric Bavier
2016-06-02 14:58 ` Jeremy Robst
2016-06-03 8:37 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-10-11 8:57 Thomas Danckaert
2016-10-12 12:54 ` Ludovic Courtès
2016-10-12 18:50 ` Thomas Danckaert
2016-10-12 20:28 ` Ludovic Courtès
2016-10-14 8:11 ` Andreas Enge
2016-10-14 11:13 ` Thomas Danckaert
[not found] ` <20161014.110029.603260973900204345.post@thomasdanckaert.be>
2016-10-16 15:05 ` Andreas Enge
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=eb7b24f7912f3027cf3a0103e898745d@openmailbox.org \
--to=ericbavier@openmailbox.org \
--cc=guix-devel-bounces+ericbavier=openmailbox.org@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jpro@bas.ac.uk \
/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).