Talk:Overlays: Difference between revisions
Latest comment: 3 August 2022 by Toraritte in topic TODOs
imported>Danidiaz About the use of "rec" in some examples. |
imported>AleXoundOS overriding of Go packages |
||
| Line 3: | Line 3: | ||
* The Python Packages Overlay uses a recursive set, and "pythonPackages = python.pkgs;" instead of "pythonPackages = self.python.pkgs;" Doesn't that mean that if a later overlay further modifies the "python" key, then " pythonPackages = python.pkgs;" will still see the earlier version? About the dangers of "rec" in overlays: https://www.youtube.com/watch?v=W85mF1zWA2o&t=681s | * The Python Packages Overlay uses a recursive set, and "pythonPackages = python.pkgs;" instead of "pythonPackages = self.python.pkgs;" Doesn't that mean that if a later overlay further modifies the "python" key, then " pythonPackages = python.pkgs;" will still see the earlier version? About the dangers of "rec" in overlays: https://www.youtube.com/watch?v=W85mF1zWA2o&t=681s | ||
* Overriding of Go packages is needed, because it's not obvious. | |||
Latest revision as of 18:10, 15 February 2023
TODOs
- the rust manual link is not valid and the Rust nightly overlay points to Mozilla's nixpkgs fork (from @fricklerhandwerk on Matrix) --Toraritte (talk) 14:50, 3 August 2022 (UTC)
- The Python Packages Overlay uses a recursive set, and "pythonPackages = python.pkgs;" instead of "pythonPackages = self.python.pkgs;" Doesn't that mean that if a later overlay further modifies the "python" key, then " pythonPackages = python.pkgs;" will still see the earlier version? About the dangers of "rec" in overlays: https://www.youtube.com/watch?v=W85mF1zWA2o&t=681s
- Overriding of Go packages is needed, because it's not obvious.