Skip to content

Conversation

@mankyKitty
Copy link

@mankyKitty mankyKitty commented Dec 16, 2022

From commit messages:

This makes it easier to combine/adapt overrides
in downstream dependencies. Without this, users
would need to override everything required by nix-thunk.
In case of a future update to nix-thunk, users would then
need to go through all of their own dependencies and
resolve them.

With this mechanism exposed, downstream users can get a
working set of pacakges from nix-thunk and need only
explicitly mention the actual compatibility/conflict issues
in their own builds.

This makes it easier to combine/adapt overrides
in downstream dependencies.  Without this, users
would need to override everything required by nix-thunk.
In case of a future update to nix-thunk, users would then
need to go through all of their own dependencies and
resolve them.

With this mechanism exposed, downstream users can get a
working set of pacakges from nix-thunk and need only
explicitly mention the actual compatibility/conflict issues
in their own builds.
@Ericson2314 Ericson2314 marked this pull request as draft October 3, 2024 19:51
@Ericson2314 Ericson2314 changed the title [WIP] Expose internals Expose internals Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants