aboutsummaryrefslogtreecommitdiff
path: root/src/nix-env/profiles.hh
AgeCommit message (Collapse)Author
2006-09-05* Missing #include.Eelco Dolstra
2006-09-04* Use a proper namespace.Eelco Dolstra
* Optimise header file usage a bit. * Compile the parser as C++.
2005-02-14* Refactoring. Hope this doesn't break the semantics of `-u' ;-)Eelco Dolstra
2005-01-19* Started removing closure store expressions, i.e., the explicitEelco Dolstra
representation of closures as ATerms in the Nix store. Instead, the file system pointer graph is now stored in the Nix database. This has many advantages: - It greatly simplifies the implementation (we can drop the notion of `successors', and so on). - It makes registering roots for the garbage collector much easier. Instead of specifying the closure expression as a root, you can simply specify the store path that must be retained as a root. This could not be done previously, since there was no way to find the closure store expression containing a given store path. - Better traceability: it is now possible to query what paths are referenced by a path, and what paths refer to a path.
2004-09-10* Operation `--delete-generations' to delete generations of aEelco Dolstra
profile. Arguments are either generation number, or `old' to delete all non-current generations. Typical use: $ nix-env --delete-generations old $ nix-collect-garbage * istringstream -> string2Int.
2004-02-11* When creating a new generation, also make the normal form of theEelco Dolstra
derivation (i.e., the closure store expression) a root of the garbage collector. This ensures that running `nix-collect-garbage --no-successors' is safe.
2004-02-08* A command `--switch-generation' to switch to a specific generationEelco Dolstra
of the current profile, e.g., $ nix-env --list-generations ... 39 2004-02-02 17:53:53 40 2004-02-02 17:55:18 41 2004-02-02 17:55:41 42 2004-02-02 17:55:50 (current) $ nix-env --switch-generation 39 $ ls -l /nix/var/nix/profiles/default ... default -> default-39-link * Also a command `--rollback' which is just a convenience operation to rollback to the oldest generation younger than the current one. Note that generations properly form a tree. E.g., if after switching to generation 39, we perform an installation action, a generation 43 is created which is a descendant of 39, not 42. So a rollback from 43 ought to go back to 39. This is not currently implemented; generations form a linear sequence.
2004-02-06* In `--list-generations', show what the current generation is.Eelco Dolstra
2004-02-06* A command `--list-generations' to show all generations for aEelco Dolstra
profile.
2004-02-06* More refactoring.Eelco Dolstra