ralismark
commented
1 year ago I had a go at this and came up with this. It's not the full dag-based solution, and I haven't extensively tested it, but at least it seems decently backwards compatible with the existing definition of home.sessionPath
{ config, lib, pkgs, ... }:
with lib;
let
cfg = config.home;
in {
options.home = {
sessionPath2 = mkOption {
type = with types; listOf str;
default = [ ];
description = ''
Extra directories to add to <envar>PATH</envar>.
(rest of description)
'';
};
};
config = {
# Include inherited $PATH people can mkBefore on it
home.sessionPath2 = [ "$PATH" ];
home.packages = [
(
pkgs.writeTextFile {
name = "path.sh";
destination = "/etc/profile.d/path.sh";
text = let
replaceMatch = match: lib.replaceStrings
[ ":\$${match}:" ":\$${match}" "\$${match}:" ]
[ "\${${match}:+:\$${match}:}" "\${${match}:+:\$${match}}" "\${${match}:+\$${match}:}" ];
pathvar = replaceMatch "PATH" (lib.concatStringsSep ":" cfg.sessionPath2);
in lib.optionalString (cfg.sessionPath2 != [ "$PATH" ]) ''
export PATH="${pathvar}"
'';
}
)
];
};
}If this kind of solution seems good I'm happy to clean this up and open a PR!
srid
stale[bot]
teutat3s
ambroisie
Description
Currently, the entries in
home.sessionPathare only appended to $PATH, and there is no way to add entries before the existing path. My main issue with this is that I'm unable to override binaries that are installed from other places.Adding packages to
home.packageswith the appropriate contents isn't an option if the contents of the directory I want to add to PATH is allowed to change without requiring ahome-manager switch.I see there's the following closed PRs:
The former was closed as the latter supersedes it, but the latter became stale and was eventually closed, and I'm kinda wondering if that's intentional or not?