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
I want to declare an output in perSystem.packages or perSystem that is not a package. The use case is that an upstream project (Lean4 in this example) has a function buildPackage which generates a custom set of attributes containing metadata, but the set of attributes is itself not a package. I need to expose this metadata to downstream users.
In this case I want to expose the output project. If I do this directly, I get
error: A definition for option `perSystem.x86_64-linux.packages.project' is not of type `package'. Definition values:
- In `/nix/store/id24xzy1kvigzs141gz2ncxc8n2pl0sf-source/flake.nix, via option perSystem':
{
allExternalDeps = [
{
allExternalDeps = [
{
...
Is there a way to expose this output so I can use it in another derivation in the form of mystery.packages.${system}.project?
The text was updated successfully, but these errors were encountered:
I want to declare an output in
perSystem.packages
orperSystem
that is not a package. The use case is that an upstream project (Lean4 in this example) has a functionbuildPackage
which generates a custom set of attributes containing metadata, but the set of attributes is itself not apackage
. I need to expose this metadata to downstream users.In this case I want to expose the output
project
. If I do this directly, I getIs there a way to expose this output so I can use it in another derivation in the form of
mystery.packages.${system}.project
?The text was updated successfully, but these errors were encountered: