From: Leo Famulari <leo@famulari.name>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add stress-make.
Date: Sat, 6 Aug 2016 21:59:16 -0400 [thread overview]
Message-ID: <20160807015916.GB5374@jasmine> (raw)
In-Reply-To: <9afd224fbac5196b7606f4539231ccdd@openmailbox.org>
On Tue, Aug 02, 2016 at 11:53:33AM -0500, Eric Bavier wrote:
> Hello Guix,
>
> I'm mostly looking for a second-opinion on the license of this package.
> Other comments welcome too, of course.
>
> * gnu/packages/debug.scm (stress-make): New variable.
> + (version (string-append "1.0-" revision "." (string-take commit 7)))
It appears they never made a release, so I think we should use "0.0.0"
instead of "1.0".
> + (uri (git-reference
> + (url "git://github.com/losalamos/stress-make.git")
I think it's better to use the HTTPS protocol instead of the Git
protocol, unless there is some reason not to. What do you think?
https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#The-Git-Protocol
> + (inputs
> + `(("make-src" ,(package-source gnu-make))))
How about "make-source", since we seem to shun abbreviations?
> + (arguments
> + ;; stress-make's configure script insists on having a tarball and does
> + ;; not accept a directory name instead. To let the gnu-build-system's
> + ;; patch-* phases work properly, we unpack the source first, then
> + ;; repack before the configure phase.
o_O
> + ;; stress-make wrapper is under BSD-3-modifications-must-be-indicated,
> + ;; and patched GNU Make is under its own license.
> + (license (list bsd-3 (package-license gnu-make))))))
Perhaps we should call it non-copyleft instead of bsd-3?
next prev parent reply other threads:[~2016-08-07 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 16:53 [PATCH] gnu: Add stress-make Eric Bavier
2016-08-07 1:59 ` Leo Famulari [this message]
2016-08-09 22:47 ` Eric Bavier
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=20160807015916.GB5374@jasmine \
--to=leo@famulari.name \
--cc=ericbavier@openmailbox.org \
--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 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.