You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So then first the translator runs and then the dependencies can be patched before the cycle detection.
That way you can use the translator to determine the package details by adding the missing dep to the root dependencies and letting the translator resolve the impurity.
This could also be used to force using a certain version of a package etc.
For even more flexibility, the sources could also be passed into the function (or to a separate function) so they can be patched too.
The text was updated successfully, but these errors were encountered:
It would also be great if this could be integrated with the overrides system. So then a known-broken package can always have the correct dependency injected.
Currently the way to inject dependencies manually is using the inject parameter as seen in the example of the main readme.
This is currently injected at evaluation time after translation. This will work with any translator and does not need to be supported by a translator.
Also for some translators, it is possible to add extra dependencies via argument. For example the pip translator allows specifying extraSetupDeps.
We do not have a way of adding deps via the override system so far. Maybe this could be integrated better. But I think first, we should have a proper module system in place before extending the current hacky API any more.
There were some discussions here: #156
And I recently opened a PR to move functionality to nixos modules: #249
Closing as injecting existing dependencies is already possible.
There are issues tracking improvements: #361
If there are some other specific things we need to improve, let's open a specific issue for that
To fix packages that don't specify all their dependencies, it would be nice to have access to the dependencies so that you could do something like
So then first the translator runs and then the dependencies can be patched before the cycle detection.
That way you can use the translator to determine the package details by adding the missing dep to the root dependencies and letting the translator resolve the impurity.
This could also be used to force using a certain version of a package etc.
For even more flexibility, the sources could also be passed into the function (or to a separate function) so they can be patched too.
The text was updated successfully, but these errors were encountered: