| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This resolves, e.g., the errors occurring when passing empty arguments
like `--option builders ''`.
Closes #967
|
| | |
| |
| |
| |
| |
| | |
This sets the state version in recent installs to the latest released
version. It is beneficial for people to be aware of this option and it
is also good to help new users get a more recent setup.
|
| | |
| |
| |
| | |
Fixes #312
|
| |\| |
|
| |/
|
|
|
|
| |
git-subtree-dir: home-manager
git-subtree-mainline: 919d4e75699aa4ba456fd2d3d416a0522c9c7294
git-subtree-split: 8bddc1adab0f7a51476f819fa2197353e8e1d136
|
| |
|
|
| |
Fixes #784
|
| |
|
|
| |
These options will be passed through to the `nix-build` tool.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This commit adds a "build" command to the install derivation that
tells the user that `nix-shell` should be used.
A derivation attribute `shellHookOnly = true` is also added with the
intent to indicate that the shell hook is the entire point of the
derivation.
|
| |
|
|
|
|
|
|
|
|
|
| |
This rewrite allows "long options" but unfortunately does not allow
merged options such as `-vn`.
Also improve the home-manager manual page, with this it should include
all sub-commands and arguments.
Finally, include the home-manager manual page in the generated HTML
documentation.
|
| |
|
|
|
|
|
|
| |
When a configuration file would be written to an existing file, rather
than failing switch (and having the user have to move or delete those
files), move the files automatically to a new path.
Closes #585
|
| | |
|
| | |
|
| |
|
|
|
| |
An error message about the erroneous option is already printed by
`getopts` so there is no need to print it again.
|
| | |
|
| |
|
|
|
|
|
| |
Instead use `runCommand`, which by default uses `stdenvNoCC` resulting
in a reduced dependency footprint.
Fixes #612
|
| |
|
|
|
|
|
|
|
|
|
| |
With this change, running
home-manager edit
opens `$HOME_MANAGER_CONFIG` in `$EDITOR`.
This is mainly for convenience. Users should not have to remember the
exact location of the Home Manager configuration.
|
| |
|
|
|
|
| |
This avoids the uncontrollable nature of fetching the tarball as part
of the evaluation. Instead the user can decide when to update and also
perform rollbacks, if necessary.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This adds a new command to the home-manager shell script that allows
generations to be removed that are older than an given absolute or
relative date.
This allows users to manage the expiration of their home-manager
generations separately from their system or user profiles via
nix-collect-garbage. It is most important if the user desires to have
a convenient way to have different expiration times for Home Manager
generations than other system or user profiles.
|
| |
|
|
| |
Fixes #352
|
| |
|
|
|
|
|
|
| |
In particular, don't bother attempting to do substitution of the home
files and home generation derivations since these rarely, if ever,
could be substituted.
Fixes #330
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It was previously possible to create the news information and lose it
in a Nix GC before being able to view it. This also causes a switch to
error out. This change makes the news information a root in the
garbage collector.
Note, this change also removes the need for `nix eval` so the
`doBuildAttr` function is simplified accordingly.
Fixes #327
|
| |
|
|
|
|
|
|
|
|
| |
Home Manager needs an absolute and resolved path to its configuration
file. The default configuration path is absolute but not necessarily
resolved. For example, some users may have `~/.config` be a symbolic
link to somewhere else. We therefore run the default configuration
path through the `realpath` tool to resolve it.
Fixes #304
|
| |
|
|
|
|
| |
This adds an experimantal, undocumented, and unsupported flag `-2` for
the `home-manager` command that enables the use of the new `nix`
command instead of `nix-build`.
|
| |
|
|
|
| |
Before, the output of `home-manager generations` would be colorized
even when used in a pipeline.
|
| |
|
|
|
| |
This new order allows overriding the home-manager path from the
command line using `home-manager -I home-manager=/a/b/c`.
|
| | |
|
| | |
|
| |
|
|
|
| |
"set -u" treats unset variables as an error, and $1 is unbound when no
command is passed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This changes the installation command from
nix-shell $HM_PATH -A install --run 'home-manager switch'
to
nix-shell $HM_PATH -A install
The added shell hook will print some useful information and run
`home-manager switch`.
|
| |
|
|
|
| |
This is a special case to work around the lack of long options in
`getopts`.
|
| |
|
|
|
| |
This command allows the user to immediately remove specific
generations from the profiles directory.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This produces a clearer error message than produced by Nix.
Fixes #116.
|
| |
|
|
|
|
| |
When using `import` to inject the configuration into the module system
we lose the location in error messages, i.e., it just says
``<unknown-file>'`.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this path would point to the modules path. Using the project
root instead makes it possible to set `<home-manager>` to point to a
downloadable archive of Home Manager. This should make it
significantly easier to install and keep Home Manager up to date.
To match this change we also deprecate the Home Manager option
programs.home-manager.modulesPath
and instead ask users to use
programs.home-manager.path
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- Rename the build function.
- Specify the built attribute in the build function.
- Make the news build silent.
|
| |
|
|
|
|
|
|
| |
This command allows the user to examine the news items generated by
the news module. See #52.
Many thanks to @nonsequitur and @uvNikita for suggestions and
improvements.
|
| |
|
|
|
|
|
| |
Using `--no-out-link` is convenient but it does not set up a GC root,
so an unfortunately timed GC could remove the generation before
activation completes. Many thanks to @nonsequitur for noting this
problem.
|
