Re: filebench: bison generated parser + CDDL
Hi!
Am Montag, 7. Mai 2012 schrieb Martin Steigerwald:
> Hi!
>
> Alex and I almost finished packaging filebench:
>
> VCS is at:
>
> Vcs-Git: git://git.debian.org/collab-maint/filebench.git
> Vcs-Browser:
> http://git.debian.org/?p=collab-maint/filebench.git;a=summary
>
> There is some licensing questions left:
>
> 1) Most files use:
>
> * CDDL HEADER START
> *
> * The contents of this file are subject to the terms of the
> * Common Development and Distribution License (the "License").
> * You may not use this file except in compliance with the License.
> *
> * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
> * or http://www.opensolaris.org/os/licensing.
> * See the License for the specific language governing permissions
> * and limitations under the License.
> *
> * When distributing Covered Code, include this CDDL HEADER in each
> * file and include the License file at usr/src/OPENSOLARIS.LICENSE.
> * If applicable, add the following below this CDDL HEADER, with the
> * fields enclosed by brackets "[]" replaced with your own identifying
> * information: Portions Copyright [yyyy] [name of copyright owner]
> *
> * CDDL HEADER END
>
> template header.
>
> Is it safe to assume that this refers to CDDL-1.0 as in:
>
> http://opensource.org/licenses/CDDL-1.0
>
> Well
>
> http://hub.opensolaris.org/bin/download/Main/licensing/cddllicense.txt
>
> refers to that version of the license as well. So that seems to be the
> case.
>
> Except for this notice:
>
> NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTION
> LICENSE (CDDL)
>
> The OpenSolaris code released under the CDDL shall be governed by the
> laws of the State of California (excluding conflict-of-law
> provisions). Any litigation relating to this License shall be subject
> to the jurisdiction of the Federal Courts of the Northern District of
> California and the state courts of the State of California, with venue
> lying in Santa Clara County, California.
>
>
> 2) It uses a bison generated parser from parser_gram.y and these
> generated files are:
>
> Files: parser_gram.c parser_gram.h
> Copyright: 1984, 1989, 1990, 2000-2011 Free Software Foundation, Inc.
> C LALR(1) parser skeleton written by Richard Stallman, by
> simplifying the original so-called "semantic" parser.
> License: GPL-3+ with exception
> This package is free software; you can redistribute it and/or modify
> […]
> You should have received a copy of the GNU General Public License
> along with this program. If not, see <http://www.gnu.org/licenses/>
> .
> On Debian systems, the complete text of the GNU General
> Public License version 3 can be found in
> "/usr/share/common-licenses/GPL-3". .
> As a special exception, you may create a larger work that contains
> part or all of the Bison parser skeleton and distribute that work
> under terms of your choice, so long as that work isn't itself a
> parser generator using the skeleton or a modified version thereof
> as a parser skeleton. Alternatively, if you modify or redistribute
> the parser skeleton itself, you may (at your option) remove this
> special exception, which will cause the skeleton and the resulting
> Bison output files to be licensed under the GNU General Public
> License without this special exception.
> .
> This special exception was added by the Free Software Foundation in
> version 2.2 of Bison.
>
>
> Is this compatible with CDDL-1?
>
> As far as I understand CDDL-1 and GPL are not compatible, but when I
> read this special exception correctly, in the case that no new parser
> generator is done any terms, any license can be used for the resulting
> work.
>
> Would it make sense to include an URL to the license in the copyright
> file? I did not see an extra field in the machine readable file format
> description, but I could always include it at the end of the license
> text if thats wanted.
Any answer on that one that allows Alex and me to proceed?
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: