Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@corinthia.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAK2iWdTOSfxNQvKctG1BJjw7eEWens-6ubkyCoYiwKMOKkLYSA@mail.gmail.com>
References: <E5B47994-873B-42F4-BD81-6D72E2340043@apache.org>
	<CAK2iWdTOSfxNQvKctG1BJjw7eEWens-6ubkyCoYiwKMOKkLYSA@mail.gmail.com>
Date: Mon, 17 Aug 2015 17:02:53 +0200
Message-ID: 
 <CAK2iWdR1JSu516it_uYDbc2F+SnCgmMCispuOjJ=SrVTQ-QVcQ@mail.gmail.com>
Subject: Re: Is using Bison & Flex ok?
From: jan i <jani@apache.org>
To: jan i <jani@apache.org>
Cc: "dev@corinthia.incubator.apache.org" <dev@corinthia.incubator.apache.org>
Content-Type: multipart/alternative; boundary=047d7bb04fbe8c7251051d831875

--047d7bb04fbe8c7251051d831875
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Monday, August 17, 2015, jan i <jani@apache.org> wrote:

>
>
> On Monday, August 17, 2015, Peter Kelly <pmkelly@apache.org
> <javascript:_e(%7B%7D,'cvml','pmkelly@apache.org');>> wrote:
>
>> I=E2=80=99m currently doing writing some experimental code for developin=
g &
>> testing a type inference algorithm that will eventually become of Flat.
>> Because the latter is not at a sufficient stage of maturity, I=E2=80=99m=
 using
>> Bison & Flex to parse a simple C-like programming language upon which I=
=E2=80=99m
>> doing the analysis.
>>
>> I=E2=80=99d like to include this code in the repository, but wanted to c=
onfirm
>> whether this is within the legal guidelines for dependent software. Biso=
n
>> is GPL, but has a special exception for the generated code (which contai=
ns
>> part of Bison itself):
>>
>> https://www.gnu.org/software/bison/manual/html_node/Conditions.html
>>
>> Flex=E2=80=99s license appears to be BSD(-like), which I=E2=80=99m assum=
ing should be ok:
>>
>> http://flex.sourceforge.net/manual/Copyright.html#Copyright
>>
>> My use of both of these tools is for experimental purposes only - my
>> intention is for Flat to eventually subsume both. I do not anticipate th=
at
>> we would include the code that requires these for building as part of an
>> actual Corinthia release.
>>
>> Tools are not a concern for. a release, the source files are, having rea=
d
> the 2 copy rigths I do not see a problem to include the files.
>
> To avoid a tedious discussion with Dennis just do it, without putting
> attention on it.
>
apologies this remark was not intented to go public, I have no wish to hang
out people by name.

however our continued licensing discussions are getting tiresome, and do
not bring us forward.

rgds
jan i

>
> Later when it comes to release time we might need to dig deeper into the
> bison license. For now it is close enough that I can truthfully say I do
> not see a problem.
>
> rgds
> jan i
>
>> Note also that these tools are required at build time only, and do not
>> require extra libraries to be distributed with the generated code.
>>
>> =E2=80=94
>> Dr Peter M. Kelly
>> pmkelly@apache.org
>>
>> PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-ke=
y
>> >
>> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
>>
>>
>
> --
> Sent from My iPad, sorry for any misspellings.
>


--=20
Sent from My iPad, sorry for any misspellings.

--047d7bb04fbe8c7251051d831875--