diff options
| author | Adam Joseph <adam@westernsemico.com> | 2022-03-28 20:51:34 -0700 |
|---|---|---|
| committer | Alexander Foremny <aforemny@posteo.de> | 2022-05-30 16:27:34 +0800 |
| commit | 81bc106e080e56e2c85466ea7d4ecf38bc99149c (patch) | |
| tree | 1365f3a05374025cd24cedff7ea3547eebbd49fd /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 9d0784829a1dabe24b186c976502a6642f99997c (diff) | |
meta.sourceProvenance documentation: clarify it is unaffected by changes to meta.license
This commit clarifies that the meaning of the `meta.sourceProvenance`
field is independent of and unaffected by the value of the
`meta.license` field. This is based on the intent of the RFC author
as expressed here:
https://github.com/NixOS/nixpkgs/pull/161098#issuecomment-1081270201
This clarification is added for two reasons:
1. If in the future there should be some disagreement about what
`sourceProvenance` to assign to a package, this may help resolve
the disagreement. Any interpretation of `sourceProvenance` which
is influenced by the `meta.license` is clearly an incorrect
interpretation.
2. If it should turn out that it is impossible to disentangle
`sourceProvenance` from `meta.license`, this would indicate the
need for changes to the `sourceProvenance` scheme. That change
might be as simple as replacing the sentence added by this commit
with some other sentence explaining how the two fields influence
each other.
This commit implements the recommendation made in the paragraph of
this comments which begins with "Please say this explicitly...":
https://github.com/NixOS/nixpkgs/pull/161098#issuecomment-1081309089
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions