Parse `.drv` to learn more information about a derivation #58

New issue

Open

opened 2023-12-05 06:59:35 +00:00 by RaitoBezarius · 2 comments

RaitoBezarius commented

2023-12-05 06:59:35 +00:00

(Migrated from github.com)

In addition to #8, it seems clear that we cannot pass the opportunity to grab the treasure of information
that is env inside of a derivation.

It contains the following information we don't have right now:

pname
version
patches

Those are critical for our operations and should be obtained during evaluation import, we should also parse every .drv directly and maybe store the full env structure as a JSONField of NixDerivation.

In addition to #8, it seems clear that we cannot pass the opportunity to grab the treasure of information that is `env` inside of a derivation. It contains the following information we don't have right now: - `pname` - `version` - `patches` Those are critical for our operations and should be obtained during evaluation import, we should also parse every `.drv` directly and maybe store the full `env` structure as a JSONField of `NixDerivation`.

fricklerhandwerk commented

2024-09-20 08:47:51 +00:00

(Migrated from github.com)

One could write Python bindings to Tvix that expose the drv parser from the nix-compat crate.

fricklerhandwerk commented

2024-11-28 16:19:28 +00:00

(Migrated from github.com)

Shifting this further out of scope for now. While it's good to have more detailed data, it's not critical for the prototype.