32f41458c0
This splits the pure content-addressed layers from tvix-store into a `castore` crate, and only leaves PathInfo related things, as well as the CLI entrypoint in the tvix-store crate. Notable changes: - `fixtures` and `utils` had to be moved out of the `test` cfg, so they can be imported from tvix-store. - Some ad-hoc fixtures in the test were moved to proper fixtures in the same step. - The protos are now created by a (more static) recipe in the protos/ directory. The (now two) golang targets are commented out, as it's not possible to update them properly in the same CL. This will be done by a followup CL once this is merged (and whitby deployed) Bug: https://b.tvl.fyi/issues/301 Change-Id: I8d675d4bf1fb697eb7d479747c1b1e3635718107 Reviewed-on: https://cl.tvl.fyi/c/depot/+/9370 Reviewed-by: tazjin <tazjin@tvl.su> Reviewed-by: flokli <flokli@flokli.de> Autosubmit: flokli <flokli@flokli.de> Tested-by: BuildkiteCI Reviewed-by: Connor Brewster <cbrewster@hey.com>
58 lines
1.9 KiB
Protocol Buffer
58 lines
1.9 KiB
Protocol Buffer
// SPDX-License-Identifier: MIT
|
|
// Copyright © 2022 The Tvix Authors
|
|
syntax = "proto3";
|
|
|
|
package tvix.store.v1;
|
|
|
|
import "tvix/castore/protos/castore.proto";
|
|
|
|
option go_package = "code.tvl.fyi/tvix/store/protos;storev1";
|
|
|
|
// PathInfo shows information about a Nix Store Path.
|
|
// That's a single element inside /nix/store.
|
|
message PathInfo {
|
|
// The path can be a directory, file or symlink.
|
|
tvix.castore.v1.Node node = 1;
|
|
|
|
// List of references (output path hashes)
|
|
// This really is the raw *bytes*, after decoding nixbase32, and not a
|
|
// base32-encoded string.
|
|
repeated bytes references = 2;
|
|
|
|
// see below.
|
|
NARInfo narinfo = 3;
|
|
}
|
|
|
|
// Nix C++ uses NAR (Nix Archive) as a format to transfer store paths,
|
|
// and stores metadata and signatures in NARInfo files.
|
|
// Store all these attributes in a separate message.
|
|
//
|
|
// This is useful to render .narinfo files to clients, or to preserve/validate
|
|
// these signatures.
|
|
// As verifying these signatures requires the whole NAR file to be synthesized,
|
|
// moving to another signature scheme is desired.
|
|
// Even then, it still makes sense to hold this data, for old clients.
|
|
message NARInfo {
|
|
// This represents a (parsed) signature line in a .narinfo file.
|
|
message Signature {
|
|
string name = 1;
|
|
bytes data = 2;
|
|
};
|
|
|
|
// This size of the NAR file, in bytes.
|
|
uint64 nar_size = 1;
|
|
|
|
// The sha256 of the NAR file representation.
|
|
bytes nar_sha256 = 2;
|
|
|
|
// The signatures in a .narinfo file.
|
|
repeated Signature signatures = 3;
|
|
|
|
// A list of references. To validate .narinfo signatures, a fingerprint
|
|
// needs to be constructed.
|
|
// This fingerprint doesn't just contain the hashes of the output paths of
|
|
// all references (like PathInfo.references), but their whole (base)names,
|
|
// so we need to keep them somewhere.
|
|
repeated string reference_names = 4;
|
|
|
|
}
|