diff options
| author | John Ericson <John.Ericson@Obsidian.Systems> | 2018-07-05 20:19:07 -0400 |
|---|---|---|
| committer | John Ericson <John.Ericson@Obsidian.Systems> | 2018-07-09 12:33:43 -0400 |
| commit | 0eb142cd46e8a46eb61fe41e1b916ffe0ec3e0ba (patch) | |
| tree | cb6cce646a8fc89c49e13048ca2c03b6c7ef4fca /pkgs/development/python-modules/GitPython/hardcode-git-path.patch | |
| parent | 48ccdf322d9e7a68d0caf5833511ee3e53ec7d3a (diff) | |
top-level: Expose `splicePackages` for `newScope` users
Otherwise extra packages in scope can't be made to work for cross. As
much as I think splicing is an evil trick, I think it's best to do this
and at least have it work consistently for now.
It would seems simpler to expose a `newScopeWithSplicing`, but there's a
few attrs (like `buildPackages` or `buildHaskellPackages`) that
shouldn't be spliced. Users should instead splice, override the splicing
on those packages, and apply `newScope` to that.
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions