New license-files field. #1642

Merged
merged 1 commit into from Jan 8, 2014

4 participants

@dcoutts
Haskell member

Based closely on the patches by Mathieu Boespflug mboes@cs.mcgill.ca

This field is intended to be used instead of (or in addition to) the
normal 'license-file' field by packages that have multiple files for
their license material. This is useful when eg the license is
supplemented by additional permissions and/or conditions. Notably,
the LGPL is structured in this way: it amends the GPL with additional
permissions, therefore one should distribute both the GPL in COPYING
and the LGPL in COPYING.LESSER.

So we keep both the license-file and license-files fields (rather than
deprecating one) and packages can use either or a mixture.

@dcoutts dcoutts New license-files field.
Based closely on the patches by Mathieu Boespflug <mboes@cs.mcgill.ca>

This field is intended to be used instead of (or in addition to) the
normal 'license-file' field by packages that have multiple files for
their license material. This is useful when eg the license is
supplemented by additional permissions and/or conditions. Notably,
the LGPL is structured in this way: it amends the GPL with additional
permissions, therefore one should distribute both the GPL in COPYING
and the LGPL in COPYING.LESSER.

So we keep both the license-file and license-files fields (rather than
deprecating one) and packages can use either or a mixture.
a7b58b1
@23Skidoo
Haskell member

LGTM.

@tibbe
Haskell member

👍

@23Skidoo 23Skidoo merged commit 66f862f into haskell:master Jan 8, 2014

1 check passed

Details default The Travis CI build passed
@amigalemming

I thought that the policy so far was to "mappend" fields if a field occurs multiple times. Thus, how about just allowing multiple License-File fields?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment