-
Licensing was incorrect, incomplete, and at best, ambiguous. Some recipes were picking one license when there were many, others were listing all the licenses and you had to pick one. On the other hand, many projects are licensed under multiple BSD-like licenses, and you must adhere to the terms of all of them, and there was no way to know how from the binary packages. Now we have an extended syntax for declaring the licensing properties of a recipe. The licenses array can now also contain dictionaries with License enums as keys and relative paths to files in the source tree as values. All files specified in this way will be copied into `share/licenses/$recipe_name`. Common license texts which are copied verbatim by projects without adding any specific author/copyright information have been copied into `data/licenses/` and will be copied into `share/licenses/$recipe_name` when a license is specified without a corresponding source tree file. `share/lic...