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
As my nixpkgs grows bigger, I plan to also generate metadata for each of the packages I defined. Using passthru in sources.toml isn't very helpful because it assume whatever value that it takes is a string, thus preventing greater control of the generated nix expr. I suppose a separate meta attribute would suffice (including more type support).
Maybe Nix could also be used interchangeably with toml? Though I would be fine if I can just evaluate Nix into toml and use that instead.
The text was updated successfully, but these errors were encountered:
danielphan2003
changed the title
Feature support: metadata passthrough / more type support
Feature request: metadata passthrough / more type support
Dec 20, 2021
I also considered about this question. Currently we use string interpolation to generate nix expr, which is not neat and error-prone. If we could create the expression programmatically, i.e. constructing and pretty printing the AST, it won't be hard to transpile toml to according nix expression.
As my nixpkgs grows bigger, I plan to also generate metadata for each of the packages I defined. Using
passthru
in sources.toml isn't very helpful because it assume whatever value that it takes is a string, thus preventing greater control of the generated nix expr. I suppose a separatemeta
attribute would suffice (including more type support).Maybe Nix could also be used interchangeably with toml? Though I would be fine if I can just evaluate Nix into toml and use that instead.
The text was updated successfully, but these errors were encountered: