nix-super/src/nix-env/user-env.hh

#pragma once
///@file

#include "get-drvs.hh"

namespace nix {

PackageInfos queryInstalled(EvalState & state, const Path & userEnv);

bool createUserEnv(EvalState & state, PackageInfos & elems,
    const Path & profile, bool keepDerivations,
    const std::string & lockToken);

}
Use "#pragma once" to prevent repeated header file inclusion 2012-07-18 21:59:03 +03:00			`#pragma once`
Ensure all headers have `#pragma once` and are in API docs `///@file` makes them show up in the internal API dos. A tiny few were missing `#pragma once`. 2023-04-01 06:18:41 +03:00			`///@file`
* Refactoring: move the user environment stuff into its own module. 2010-04-19 13:47:56 +03:00
			`#include "get-drvs.hh"`

			`namespace nix {`

DerivationInfo -> PackageInfo This does not yet resolve the coupling between packages and derivations, but it makes the code more consistent with the terminology, and it accentuates places where the coupling is obvious, such as auto drvPath = packageInfo.queryDrvPath(); if (!drvPath) throw Error("'%s' is not a derivation", what()); ... which isn't wrong, and in my opinion, doesn't even look wrong, because it just reflects the current logic. However, I do like that we can now start to see in the code that this coupling is perhaps a bit arbitrary. After this rename, we can bring the DerivingPath concept into type and start to lift this limitation. 2024-01-16 16:25:04 +02:00			`PackageInfos queryInstalled(EvalState & state, const Path & userEnv);`
* Refactoring: move the user environment stuff into its own module. 2010-04-19 13:47:56 +03:00
DerivationInfo -> PackageInfo This does not yet resolve the coupling between packages and derivations, but it makes the code more consistent with the terminology, and it accentuates places where the coupling is obvious, such as auto drvPath = packageInfo.queryDrvPath(); if (!drvPath) throw Error("'%s' is not a derivation", what()); ... which isn't wrong, and in my opinion, doesn't even look wrong, because it just reflects the current logic. However, I do like that we can now start to see in the code that this coupling is perhaps a bit arbitrary. After this rename, we can bring the DerivingPath concept into type and start to lift this limitation. 2024-01-16 16:25:04 +02:00			`bool createUserEnv(EvalState & state, PackageInfos & elems,`
* Store user environment manifests as a Nix expression in $out/manifest.nix rather than as an ATerm. (Hm, I thought I committed this two days ago...) 2010-04-21 18:08:58 +03:00			`const Path & profile, bool keepDerivations,`
Remove std::string alias (for real this time) Also use std::string_view in a few more places. 2022-02-25 17:00:00 +02:00			`const std::string & lockToken);`
* Store user environment manifests as a Nix expression in $out/manifest.nix rather than as an ATerm. (Hm, I thought I committed this two days ago...) 2010-04-21 18:08:58 +03:00
* Refactoring: move the user environment stuff into its own module. 2010-04-19 13:47:56 +03:00			`}`