From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: octave license is incompatible with openssl Date: Mon, 8 Aug 2016 16:00:18 -0400 Message-ID: <20160808200018.GA20179@jasmine> References: <87h9b0ij9x.fsf@gmail.com> <87wpjvhfpg.fsf@elephly.net> <87eg62d5p4.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bWqix-0004Dp-Rz for guix-devel@gnu.org; Mon, 08 Aug 2016 16:00:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bWqit-0008Jn-JL for guix-devel@gnu.org; Mon, 08 Aug 2016 16:00:34 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:52821) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bWqis-0008JV-Cp for guix-devel@gnu.org; Mon, 08 Aug 2016 16:00:31 -0400 Content-Disposition: inline In-Reply-To: <87eg62d5p4.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Alex Vong Cc: guix-devel@gnu.org On Sat, Aug 06, 2016 at 09:52:39AM +0800, Alex Vong wrote: > Ricardo Wurmus writes: > > > Alex Vong writes: > > > >> 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). > > > > Looks like you’re right. Other projects add a special openSSL linking > > exception, but Octave does not seem to account for this. > > > >> How should we fix this? > > > > It seems that the use of openssl in Octave is optional, so we could > > probably just remove it. From a cursory look it appears that it is used > > for not much more than the MD5 algorithm. Would you like to submit a > > patch that removes openssl from the inputs? > > > Here it is. It takes a long time to track down that curl is pulling the > openssl depedency. I also upgrade octave to 4.0.3 and change to use > 'tar.xz'. > > > It would be good to ask the Octave project if it would be possible to > > replace OpenSSL with, say, GnuTLS. > > > I agree, should we CC/forward this discussion to octave-devel list? Yes, I think we should work with them to resolve this issue.