From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3320 invoked by alias); 29 Jul 2003 01:00:00 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 3302 invoked from network); 29 Jul 2003 00:59:59 -0000 Received: from unknown (HELO ms-smtp-03.southeast.rr.com) (24.93.67.84) by sources.redhat.com with SMTP; 29 Jul 2003 00:59:59 -0000 Received: from lyta.haphazard.org (rdu57-9-048.nc.rr.com [66.57.9.48]) by ms-smtp-03.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h6T0w193012005; Mon, 28 Jul 2003 20:58:02 -0400 (EDT) Received: by lyta.haphazard.org (Postfix, from userid 500) id 4AFD2BE6B4; Mon, 28 Jul 2003 20:59:55 -0400 (EDT) To: PureNative Software Cc: mauve-discuss@sources.redhat.com Subject: Re: Using Mauve for Our Project References: <00d301c35259$2c0c5ac0$9865fea9@yourviu5vcdub5> From: Brian Jones Date: Tue, 29 Jul 2003 01:00:00 -0000 In-Reply-To: <00d301c35259$2c0c5ac0$9865fea9@yourviu5vcdub5> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q3/txt/msg00005.txt.bz2 PureNative Software writes: > We have been using Mauve internally for some time now and are really > benefiting from it. In fact, we have converted the entire Mauve > project to native C++. We are wishing to make this native C++ > version of Mauve available as open source to the public. However, > ... compiling our C++ version of Mauve requires our NewJ Library > header files and static library, which are not open source. Is it > permissible for us to distribute our C++ version of Mauve to the > public without the underlying library being open source? Your question is more appropriate for a lawyer. While I don't have a use for it, having more Mauve goodness open to the public is a plus in my book, for what it's worth. Brian -- Brian Jones