On Wed, Dec 23, 2015 at 10:21 PM, Wen Lin <[email protected]> wrote:
> Hi, Roman,
>
> For these lines, I can make it more specific to some subtree.
> <exclude>**/*.mk</exclude>
> <exclude>**/*.mak</exclude>
> <exclude>**/*.yaml</exclude>
> <exclude>**/*.m4</exclude>
> <exclude>config/*</exclude>
> <exclude>**/*.rc</exclude>
> <exclude>**/*.f</exclude>
> <exclude>**/Makefile*</exclude>
> For the other files, if it is too long to read, what do you suggest make it
> simple?
> For example, in src/backend/executor, some files belong to Postgres, some
> files belong to Apache in same directory.
>
> It is hard to write a wildcard expression which can exclude Postgres files,
> unless Iist all the files belong to Postgres in exclude file.
I've been thinking that perhaps we can automate the PG-derived
code detection process by including something like the snippet
bellow in pom.xml.
That'll give us part of the solution. Some of the files that were derived
from PG now carry Greenplum, EMC and Pivotal copyrights. For those
files an explicit ALv2 header will be required.
> There are a lot of similar situations like this. That's why the exclude
> list is very long.
> Do you have any idea for handling this?
Personally, I'd like to leverage RAT as much as possible here for
actually detecting licenses, not just excluding files. I know my
suggestion below may not be bullet proof, so I'd love to know
what other mentors think about it.
Thanks,
Roman.
RAT configuration snippet:
<licenses>
<license
implementation="org.apache.rat.analysis.license.SimplePatternBasedLicense">
<licenseFamilyCategory>PGSQL</licenseFamilyCategory>
<licenseFamilyName>PostgreSQL License</licenseFamilyName>
<notes></notes>
<patterns>
<pattern>$PostgreSQL:</pattern>
<pattern>PostgreSQL Global Development Group</pattern>
</patterns>
</license>
</licenses>
