Add instructions for LICENSE and LICENSE_FILE to the Porter's Handbook

[rwestlun_gmail.com]

Summary

There doesn't seem to be documentation in the Porter's Handbook about LICENSE and LICENSE_FILE. This patch adds a new section for it. This should be reviewed by a ports committer for correctness.

[woodsb02]

I think this is a good start to adding a LICENSE section - thank you for the contribution. Not necessarily with this commit, but later it should be expanded to include details of MULTI and DUAL, etc.

[wblock]

en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml

3315

"let the ports infrastructure know" is kind of vague. Also, this port might have any code, but still could have a license.

Maybe:

Set <varname>LICENSE</varname> to identify the license used by this port.

Issues:

• telling people not to create new copies of licenses (this is mentioned somewhere else, don't recall where
• what if a port has dual licensing?
• what if different components of a port have different licenses?

[rwestlun_gmail.com]

en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml

3315

Yeah, that wording is much better.

For your second point, I intended to address this in line 3330.

Can you suggest additions to address points one and three? I don't know how to handle those.

[mat]

There is a review openned for that, D56, it just lacks some inspiration :-)

[rwestlun_gmail.com]

Oh, that's much more detailed. Also untouched for two years...

I have no attachment to my patch, but something should be committed. Figuring out the LICENSE stuff was a sticking point for me due to lack of documentation, and I still don't fully understand it.

I suggest getting something in the handbook soon and revising it later, rather than waiting for a perfectly complete section to be finished.

[linimon]

A (complete?) superset of this content was committed as rD50189. To submitter: is there anything else that should be added that I have missed?

[rwestlun_gmail.com]

That covers it, thanks!