Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-07-22 | Support --eval-store in nix-instantiate and nix-build | Eelco Dolstra | |
2021-07-22 | Add --eval-store option | Eelco Dolstra | |
2021-05-17 | Enfore the use of properly built paths in libcmd | regnat | |
Replace `DerivedPathWithHints` by a new `BuiltPath` type that serves as a proof that the corresponding path has been built. | |||
2021-05-12 | DerivedPathWithHints -> BuiltPath | regnat | |
Just a renaming for now | |||
2021-04-27 | Merge branch 'master' into debugger-merge | Ben Burdette | |
2021-04-05 | Rename Buildable | John Ericson | |
2021-03-02 | Make NIX_SHOW_STATS work with new-style commands | regnat | |
2021-02-12 | Deeper `Command` hierarchy to remove redundancy | John Ericson | |
Simply put, we now have `StorePathCommand : public StorePathsCommand` so `StorePathCommand` doesn't reimplement work. | |||
2021-01-28 | Add a new Cmd type working on RealisedPaths | regnat | |
Where a `RealisedPath` is a store path with its history, meaning either an opaque path for stuff that has been directly added to the store, or a `Realisation` for stuff that has been built by a derivation This is a low-level refactoring that doesn't bring anything by itself (except a few dozen extra lines of code :/ ), but raising the abstraction level a bit is important on a number of levels: - Commands like `nix build` have to query for the realisations after the build is finished which is fragile (see 27905f12e4a7207450abe37c9ed78e31603b67e1 for example). Having them oprate directly at the realisation level would avoid that - Others like `nix copy` currently operate directly on (built) store paths, but need a bit more information as they will need to register the realisations on the remote side | |||
2021-01-26 | Move command plugin interface to libnixcmd | Shea Levy | |