haskell-generic-builder: Expose haskell and system build inputs. #24710
Conversation
This can be used to build envs for building haskell packages that are more complicated than the default env currently exported, e.g. a single composite env that can be used to build multiple packages.
|
@shlevy, thanks for your PR! By analyzing the history of the files in this pull request, we identified @peti, @cstrahan and @expipiplus1 to be potential reviewers. |
|
@peti this is basically the work you reverted before, but as far as I can tell there's still no good way to do this. |
|
@peti ping |
There was a problem hiding this comment.
I don't like the notion of the generic builder exporting its inputs as output. It feels wrong and unnecessary considering the fact that those values are readily available without running the generic builder, i.e. one can simply override any package's mkDerivation with a function that composes and returns the desired haskellBuildInput, and such a function could live in haskell.lib and be re-usable for all kind of purposes --- including re-use by the generic builder. IMHO, that'd be a far superior approach.
|
Ah, that's a good idea, thanks. |
This can be used to build envs for building haskell packages that are
more complicated than the default env currently exported, e.g. a
single composite env that can be used to build multiple packages.