Adam Joseph 81bc106e08 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		2022-05-30 16:27:34 +08:00
..
cross-compilation.chapter.md	Update doc/stdenv/cross-compilation.chapter.md	2022-04-03 17:43:52 +00:00
meta.chapter.md	meta.sourceProvenance documentation: clarify it is unaffected by changes to meta.license	2022-05-30 16:27:34 +08:00
multiple-output.chapter.md	treewide: change some glibc to stdenv.cc.libc	2022-05-27 05:57:43 +03:00
platform-notes.chapter.md
stdenv.chapter.md	makeBinaryWrapper: move into its own folder	2022-05-10 22:07:56 +02:00