tvl-depot/tvix
Vincent Ambo fdca93d6ed feat(tvix/cli): add helper for populating derivation inputs
This adds a helper function which takes the output of the reference
scanner used on derivation inputs and populates the `input_sources`
and `input_derivations` field of the derivation accordingly.

Note that we have a divergence from C++ Nix here, as we do not
populate the entire FS closure of a literally referred derivation (and
our standing theory is that this is unnecessary for nixpkgs).

Change-Id: Id0f605dd8c0a82973c56605c2b8f478fc17777d6
Reviewed-on: https://cl.tvl.fyi/c/depot/+/7899
Tested-by: BuildkiteCI
Reviewed-by: flokli <flokli@flokli.de>
2023-01-27 12:21:41 +00:00
..
.vscode chore(tvix): fix vscode rust-analyzer recommendation 2022-10-15 16:54:28 +00:00
cli feat(tvix/cli): add helper for populating derivation inputs 2023-01-27 12:21:41 +00:00
derivation refactor(tvix/derivation): align error messages with rust style 2023-01-26 16:30:33 +00:00
docs docs(tvix): fix minor spelling problems in pointer equality document 2023-01-25 14:30:50 +00:00
eval chore(tvix/eval): remove dead comment 2023-01-26 23:30:43 +00:00
nar docs(tvix/nar): document how to use NAR writer 2022-12-21 14:31:54 +00:00
nix_cli chore(tvix): upgrade to clap 4.0 2022-12-21 13:23:38 +00:00
proto chore(tvix/store): move castore.proto 2022-12-04 10:41:39 +00:00
serde feat(tvix/serde): implement enum deserialisation 2023-01-04 17:21:40 +00:00
store chore(tvix/store): add fastcdc crate 2023-01-21 15:12:45 +00:00
verify-lang-tests test(tvix/eval): add test for builtins parity 2023-01-06 12:00:38 +00:00
.gitignore feat(tvix/): .gitignore target folders 2022-11-11 19:55:12 +00:00
Cargo.lock feat(tvix/eval): implement builtins.fromTOML 2023-01-25 07:49:44 +00:00
Cargo.nix feat(tvix/eval): implement builtins.fromTOML 2023-01-25 07:49:44 +00:00
Cargo.toml feat(tvix/serde): initial Nix->serde::Deserialize impl 2023-01-02 22:24:43 +00:00
crate-hashes.json chore(tvix/store): add tonic-mock 2023-01-21 09:34:15 +00:00
default.nix refactor(tvix/store): move protobuf build config one level up 2023-01-06 17:57:06 +00:00
LICENSE chore(tvix): Bootstrap Tvix folder 2021-03-27 00:09:49 +00:00
OWNERS chore(gerrit): migrate OWNERS files to code-owners style 2022-09-19 11:13:28 +00:00
README.md docs(tvix): link to IRC channel and mailing list 2023-01-21 15:08:38 +00:00

Tvix

For more information about Tvix, feel free to reach out. We are interested in people who would like to help us review designs, brainstorm and describe requirements that we may not yet have considered.

Most of the discussion around development happens on our IRC channel, which you can join in several ways documented on tvl.fyi.

There's also some discussion around development on our mailing list.

Building the CLI

If you are in a full checkout of the TVL depot, you can simply run mg build in the cli directory (or mg build //tvix/cli from anywhere in the repo). The mg command is found in /tools/magrathea.

Important note: We only use and test Nix builds of our software against Nix 2.3. There are a variety of bugs and subtle problems in newer Nix versions which we do not have the bandwidth to address, builds in newer Nix versions may or may not work.

The CLI can also be built with standard Rust tooling (i.e. cargo build), as long as you are in a shell with the right dependencies (provided by mg shell //tvix:shell).

Rust projects, crate2nix

Some parts of Tvix are written in Rust. To simplify the dependency management on the Nix side of these builds, we use crate2nix in a single Rust workspace in //tvix to maintain the Nix build configuration.

When making changes to Cargo dependency configuration in any of the Rust projects under //tvix, be sure to run mg run //tvix:crate2nixGenerate -- in //tvix itself and commit the changes to the generated Cargo.nix file.

License structure

All code implemented for Tvix is licensed under the GPL-3.0, with the exception of the protocol buffer definitions used for communication between services which are available under a more permissive license (MIT).

The idea behind this structure is that any direct usage of our code (e.g. linking to it, embedding the evaluator, etc.) will fall under the terms of the GPL3, but users are free to implement their own components speaking these protocols under the terms of the MIT license.