You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2017/07/24 05:00:01 UTC

[jira] [Created] (GUACAMOLE-353) Clarify ASF header within Makefile.am, etc. regarding build system output

Michael Jumper created GUACAMOLE-353:
----------------------------------------

             Summary: Clarify ASF header within Makefile.am, etc. regarding build system output
                 Key: GUACAMOLE-353
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-353
             Project: Guacamole
          Issue Type: Task
          Components: guacamole-server
            Reporter: Michael Jumper
            Priority: Minor


Pieces of the contents of {{configure.ac}}, {{Makefile.am}}, and related files are included in the build output of GNU Autotools when the source archives for Guacamole are generated, including the ASF boilerplate comment. Because autotools also inserts its own FSF boilerplate at the top of these generated files, we end up with a confusing combination of FSF and ASF headers.

This concern was brought up during the release VOTE for 0.9.12-incubating, and discussed in LEGAL-300. The final conclusion of this was:

{quote}
... 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.
{quote}

The above change should be made wherever necessary, once suitable wording has been determined.



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