According to the ASF Source Header and Copyright Notice Policy (http://www.apache.org/legal/src-headers.html), all human-readable Apache-developed files that are included within a distribution must include ASL header text. None of the source files for our config tests currently does. These headers need to be added in time for the 4.2.0 release.
Note that since in the config tests, the first line is reserved for the "label" displayed by GNUMakefile.cfg before compiling the test, the headers cannot start on the first line. Instead, it should be fine to append the header to the end of every config test instead.
Since the above mentioned policy applies to releases distributed after November 1, 2006, this task affects trunk only (and not any already published releases or snapshots).
Description
According to the ASF Source Header and Copyright Notice Policy (http://www.apache.org/legal/src-headers.html), all human-readable Apache-developed files that are included within a distribution must include ASL header text. None of the source files for our config tests currently does. These headers need to be added in time for the 4.2.0 release.
Note that since in the config tests, the first line is reserved for the "label" displayed by GNUMakefile.cfg before compiling the test, the headers cannot start on the first line. Instead, it should be fine to append the header to the end of every config test instead.
Since the above mentioned policy applies to releases distributed after November 1, 2006, this task affects trunk only (and not any already published releases or snapshots).
patches for the configuration tests, the compiler config scripts, and generate/configure.bat.
Note: I can't find the location that I read it, but the license header is supposed to be near the top of the file. I can't find a source for that information, but I did read it today while researching the requirements.
Travis Vitek added a comment - 18/Sep/07 01:52 AM patches for the configuration tests, the compiler config scripts, and generate/configure.bat.
Note: I can't find the location that I read it, but the license header is supposed to be near the top of the file. I can't find a source for that information, but I did read it today while researching the requirements.
I've successfully tested with gcc on Linux compiler-config.patch and config-tests.patch and committed both. I don't have access to Windows. Farid, can you test the last Windows-only configure.patch and, assuming it checks out, commit it?
Martin Sebor added a comment - 18/Sep/07 05:01 AM I've successfully tested with gcc on Linux compiler-config.patch and config-tests.patch and committed both. I don't have access to Windows. Farid, can you test the last Windows-only configure.patch and, assuming it checks out, commit it?
Farid, please set the issue to Resolved after you've tested the last (Windows-only) patch. We'll close it once RAT confirms that all the files are properly licensed.
Martin Sebor added a comment - 19/Sep/07 09:26 PM Assigned to Farid.
Farid, please set the issue to Resolved after you've tested the last (Windows-only) patch. We'll close it once RAT confirms that all the files are properly licensed.
Note: I can't find the location that I read it, but the license header is supposed to be near the top of the file. I can't find a source for that information, but I did read it today while researching the requirements.