A home-manager/home.nix => home-manager/home.nix +90 -0
@@ 0,0 1,90 @@
+{ config, pkgs, ... }:
+
+{
+ # Home Manager needs a bit of information about you and the paths it should
+ # manage.
+ home.username = "landhar";
+ home.homeDirectory = "/Users/landhar";
+
+ # This value determines the Home Manager release that your configuration is
+ # compatible with. This helps avoid breakage when a new Home Manager release
+ # introduces backwards incompatible changes.
+ #
+ # You should not change this value, even if you update Home Manager. If you do
+ # want to update the value, then make sure to first check the Home Manager
+ # release notes.
+ home.stateVersion = "23.11"; # Please read the comment before changing.
+
+ # The home.packages option allows you to install Nix packages into your
+ # environment.
+ home.packages = [
+ # # Adds the 'hello' command to your environment. It prints a friendly
+ # # "Hello, world!" when run.
+ # pkgs.hello
+
+ pkgs.asdf-vm
+ pkgs.elixir_1_14
+ pkgs.elmPackages.elm
+ pkgs.erlangR25
+ pkgs.eza
+ pkgs.fd
+ pkgs.just
+ (pkgs.pass.withExtensions (exts: [ exts.pass-otp ]))
+ pkgs.htop
+ pkgs.mpv
+ pkgs.python311
+ pkgs.python311Packages.beautifulsoup4
+ pkgs.python311Packages.click
+ pkgs.python311Packages.requests
+ pkgs.python311Packages.flask
+ pkgs.python311Packages.wxPython_4_2
+ pkgs.viu
+ pkgs.yt-dlp
+
+ # # It is sometimes useful to fine-tune packages, for example, by applying
+ # # overrides. You can do that directly here, just don't forget the
+ # # parentheses. Maybe you want to install Nerd Fonts with a limited number of
+ # # fonts?
+ # (pkgs.nerdfonts.override { fonts = [ "FantasqueSansMono" ]; })
+
+ # # You can also create simple shell scripts directly inside your
+ # # configuration. For example, this adds a command 'my-hello' to your
+ # # environment:
+ # (pkgs.writeShellScriptBin "my-hello" ''
+ # echo "Hello, ${config.home.username}!"
+ # '')
+ ];
+
+ # Home Manager is pretty good at managing dotfiles. The primary way to manage
+ # plain files is through 'home.file'.
+ home.file = {
+ # # Building this configuration will create a copy of 'dotfiles/screenrc' in
+ # # the Nix store. Activating the configuration will then make '~/.screenrc' a
+ # # symlink to the Nix store copy.
+ # ".screenrc".source = dotfiles/screenrc;
+
+ # # You can also set the file content immediately.
+ # ".gradle/gradle.properties".text = ''
+ # org.gradle.console=verbose
+ # org.gradle.daemon.idletimeout=3600000
+ # '';
+ };
+
+ # Home Manager can also manage your environment variables through
+ # 'home.sessionVariables'. If you don't want to manage your shell through Home
+ # Manager then you have to manually source 'hm-session-vars.sh' located at
+ # either
+ #
+ # ~/.nix-profile/etc/profile.d/hm-session-vars.sh
+ #
+ # or
+ #
+ # /etc/profiles/per-user/landhar/etc/profile.d/hm-session-vars.sh
+ #
+ home.sessionVariables = {
+ # EDITOR = "emacs";
+ };
+
+ # Let Home Manager install and manage itself.
+ programs.home-manager.enable = true;
+}
D nixpkgs/home.nix => nixpkgs/home.nix +0 -31
@@ 1,31 0,0 @@
-{ config, pkgs, ... }:
-
-{
- # Home Manager needs a bit of information about you and the
- # paths it should manage.
- home.username = "landhar";
- home.homeDirectory = "/Users/landhar";
-
- # Packages that should be installed to the user profile.
- home.packages = with pkgs; [
- asdf-vm
- elixir_1_14
- erlangR25
- exa
- (pass.withExtensions (exts: [ exts.pass-otp ]))
- htop
- ];
-
- # This value determines the Home Manager release that your
- # configuration is compatible with. This helps avoid breakage
- # when a new Home Manager release introduces backwards
- # incompatible changes.
- #
- # You can update Home Manager without changing this value. See
- # the Home Manager release notes for a list of state version
- # changes in each release.
- home.stateVersion = "22.05";
-
- # Let Home Manager install and manage itself.
- programs.home-manager.enable = true;
-}