unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: octave license is incompatible with openssl
Date: Thu, 4 Aug 2016 19:10:37 +0200	[thread overview]
Message-ID: <20160804171037.GA11676@jocasta.intra> (raw)
In-Reply-To: <87h9b0ij9x.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

I would not be at all suprised if there were more incompatibilities like
this.  Ought we not have  a lint rule that checks this?

J'

On Fri, Aug 05, 2016 at 12:35:54AM +0800, Alex Vong wrote:
     Hi guixes,
     
     First, congratulations to Ricardo Wurmus as new maintainer and the new
     0.11 release is good (it passed all tests)!
     
     I notice 'octave 4.0.2' has 'openssl@1.0.2h' as one of its inputs. As
     far as I know, gplv3 is incompatible with openssl license
     (https://people.gnome.org/~markmc/openssl-and-the-gpl.html).
     
     How should we fix this?
     
     
     Cheers,
     Alex

-- 
Avoid eavesdropping.  Send strong encryted 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 --]

  reply	other threads:[~2016-08-04 17:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 16:35 octave license is incompatible with openssl Alex Vong
2016-08-04 17:10 ` John Darrington [this message]
2016-08-04 17:20   ` ng0
2016-08-05  9:08     ` Alex Vong
2016-08-05  9:03   ` Alex Vong
2016-08-05 11:43     ` Mathieu Lirzin
2016-08-05  6:50 ` Ricardo Wurmus
2016-08-06  1:52   ` Alex Vong
2016-08-08 20:00     ` Leo Famulari
2016-08-09 16:00       ` Alex Vong
2016-08-09 17:27         ` Mike Miller
2016-08-09 18:30           ` Ricardo Wurmus
2016-08-09 21:33             ` kei
2016-08-10  4:28               ` Mark H Weaver
2016-08-11  5:56                 ` Mike Miller
2016-08-11  9:58                   ` Mark H Weaver
2016-08-10  4:23           ` Mark H Weaver
2016-08-10  6:43           ` Alex Vong
2016-08-11  6:26             ` Mike Miller
2016-08-11 15:27               ` Alex Vong
2016-08-11 17:04                 ` Kei Kebreau
2016-08-13 12:37                   ` Alex Vong
2016-08-12 11:45                 ` JIT compiling Jordi Gutiérrez Hermoso
2016-08-12 15:08                   ` Sergei Steshenko
2016-08-12 16:06                     ` Oliver Heimlich
2016-08-13  1:03                       ` Sergei Steshenko
2016-08-13 11:48                         ` Alex Vong
2016-08-13 12:12                   ` Alex Vong
2016-08-14  8:07                     ` Sergei Steshenko
2016-08-14 10:21                       ` Francesco Potortì
2016-08-14 20:20                       ` Jordi Gutiérrez Hermoso

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=20160804171037.GA11676@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=alexvong1995@gmail.com \
    --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 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).