all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Cyril Roelandt <tipecaml@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] gnu: Add sparse.
Date: Tue, 26 Feb 2013 22:35:03 +0100	[thread overview]
Message-ID: <512D2A87.5000008@gmail.com> (raw)
In-Reply-To: <87621fv6gc.fsf@gnu.org>

On 02/26/2013 09:13 AM, Ludovic Courtès wrote:
> Cyril Roelandt<tipecaml@gmail.com>  skribis:
>
>> This patch adds sparse.
>
> Thanks!  Would it make sense to put it in linux.scm?
>

It's not really Linux-specific, even though it is mainly used by Linux 
hackers. I think it's used by smatch, a static analysis tool developed 
by Dan Carpenter, that can be used on any piece of C code, for instance. 
It's also used in the test-suite of git.

>> I had to add the Open Software License to guix/licenses.scm. Debian
>> does not think of it as a Free Software license, but I think it's OK
>> with GNU.
>
> The page at<https://www.gnu.org/licenses/license-list.html#OSL>
> contains says it’s free but mentions worrisome details:
>
>     Recent versions of the Open Software License have a term which
>     requires distributors to try to obtain explicit assent to the
>     license. This means that distributing OSL software on ordinary FTP
>     sites, sending patches to ordinary mailing lists, or storing the
>     software in an ordinary version control system, is arguably a
>     violation of the license and would subject you to possible
>     termination of the license.  [...]
>
> We’re not distributing it, just distributing the build recipes.
> However, would it be a violation to distribute pre-built binaries on
> Hydra?  Could you check that?

Indeed, this is the ninth clause. Maybe I should email the current 
sparse maintainer and ask him ?

Cyril.

  reply	other threads:[~2013-02-26 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  2:16 [PATCH] gnu: Add sparse Cyril Roelandt
2013-02-26  8:13 ` Ludovic Courtès
2013-02-26 21:35   ` Cyril Roelandt [this message]
2013-02-26 22:16     ` 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=512D2A87.5000008@gmail.com \
    --to=tipecaml@gmail.com \
    --cc=bug-guix@gnu.org \
    --cc=ludo@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.