Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Thu, 13 Jul 2017 22:49:00 +0000 (UTC)
From: "Chris A. Mattmann (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.13064449.1492452798000.243820.1499986140107@Atlassian.JIRA>
In-Reply-To: <JIRA.13064449.1492452798000@Atlassian.JIRA>
References: <JIRA.13064449.1492452798000@Atlassian.JIRA> <JIRA.13064449.1492452798519@jira-lw-us.apache.org>
Subject: [jira] [Commented] (LEGAL-300) Should ASF headers be excluded from
 the auto-generated output of GNU Autotools?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 13 Jul 2017 22:49:03 -0000


    [ https://issues.apache.org/jira/browse/LEGAL-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086551#comment-16086551 ] 

Chris A. Mattmann commented on LEGAL-300:
-----------------------------------------

The resolution is:

{noformat}
To answer the original question, I would suggest simply to edit the
license header in Makefile.am such that it is correct both in situ (in
Makefile.am) and when transcluded into Makefile.in. Basically, add
a sentence or two explaining the licenses of Makefile.am and Makefile.in
and that verbatim transclusion is occuring.
{noformat}


> Should ASF headers be excluded from the auto-generated output of GNU Autotools?
> -------------------------------------------------------------------------------
>
>                 Key: LEGAL-300
>                 URL: https://issues.apache.org/jira/browse/LEGAL-300
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Michael Jumper
>            Assignee: Chris A. Mattmann
>
> Hello,
> During the release VOTE for Apache Guacamole 0.9.12-incubating, concerns were raised regarding the presence of ASF headers in the auto-generated output of the build system, in this case GNU Autotools:
> {quote}
> ...
> - There's a few files such as Makefile.in that have a mix of ASF and
> non-ASF headers, which isn't really appropriate. I also don't see the FSF
> claim in the License file.
> ...
> {quote}
> (See: https://lists.apache.org/thread.html/2f7ca58b1907698f70af06c113e36e75f2dc987e416b0a0242ab436f@%3Cgeneral.incubator.apache.org%3E)
> The "Makefile.in" file mentioned above is automatically generated by the build system based on the input file "Makefile.am". That input file does (and must) have ASF headers, as it is part of the Apache Guacamole codebase:
> https://github.com/apache/incubator-guacamole-server/blob/37fe3548de87adefe189ce48ebe4aebef3d0a18e/Makefile.am#L1-L18
> Because GNU Autotools includes verbatim portions of "Makefile.am" while generating "Makefile.in", comments from the original input file are preserved, including the ASF header. GNU Autotools also adds its own licensing header to its output, resulting in a file containing both headers:
> {code:none}
> # Makefile.in generated by automake 1.15 from Makefile.am.
> # @configure_input@
> # Copyright (C) 1994-2014 Free Software Foundation, Inc.
> # This Makefile.in is free software; the Free Software Foundation
> # gives unlimited permission to copy and/or distribute it,
> # with or without modifications, as long as this notice is preserved.
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
> # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
> # PARTICULAR PURPOSE.
> @SET_MAKE@
> #
> # Licensed to the Apache Software Foundation (ASF) under one
> # or more contributor license agreements.  See the NOTICE file
> # distributed with this work for additional information
> # regarding copyright ownership.  The ASF licenses this file
> # to you under the Apache License, Version 2.0 (the
> # "License"); you may not use this file except in compliance
> # with the License.  You may obtain a copy of the License at
> #
> #   http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing,
> # software distributed under the License is distributed on an
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> # KIND, either express or implied.  See the License for the
> # specific language governing permissions and limitations
> # under the License.
> #
> {code}
> It is not possible to exclude the FSF header that is automatically added, but it is possible to exclude the ASF header by altering the format of the comment in the input (using a leading "##" instead of "#").
> Given:
> # The FSF and ASF headers seem to conflict.
> # The ASF header can be excluded if necessary.
> # The auto-generated output file does contain verbatim portions of the input to which the ASF header should apply.
> # The auto-generated output file contains verbatim portions of the GNU Autotools build system to which the FSF header applies.
> Should the ASF headers be excluded from the auto-generated output of GNU Autotools for ASF projects using that build system?
> Thanks.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org