anirrudh has quit [Remote host closed the connection]
johnw` is now known as johnw
anirrudh has joined #home-manager
<anirrudh>
Hello, I'm having a rather simple issue on nixOS. On every reboot, I need to run home-manager switch before I can access any of my applications that are installed via home manager. If I do not, a sql db lock is complained about.
anirrudh has quit [Ping timeout: 256 seconds]
anirrudh has joined #home-manager
anirrudh has quit [Client Quit]
mexisme has joined #home-manager
c0c0 has quit [Ping timeout: 256 seconds]
c0c0 has joined #home-manager
romanofski has quit [Ping timeout: 256 seconds]
oranginal has joined #home-manager
<oranginal>
Hello, home-manager people. I was curious about why one would use home manager over a config file and would the benefits still be there on a single user system?
OrangeTetra has joined #home-manager
OrangeTetra has quit [Client Quit]
oranginal has quit [Ping timeout: 258 seconds]
luna has joined #home-manager
mexisme has quit [Ping timeout: 265 seconds]
romanofski has joined #home-manager
* Emantor
uses home-manager on a single user system and benefits from centralized configuration across multiple machines.
luna has quit [Quit: Leaving]
evax has joined #home-manager
cole-h has quit [Quit: Goodbye]
mexisme has joined #home-manager
malSet has quit [Quit: Quit.]
malSet has joined #home-manager
<rycee>
anirrudh: I'm not sure I understand. You get an lock error if you try to run an application that is installed through HM? And the lock error is resolved if you do a switch?
<rycee>
oranginal: It depends. I use HM mainly on single user systems but I deploy the configurations with various tweaks to different systems and containers.
<rycee>
If all you need is to put a few static dotfiles into place then HM would not offer much benefit over, say, GNU Stow.
<rycee>
On the other hand, if you need to generate configuration files, manage user services, deploy variations of a shared configuration to different places, then HM is quite handy.
mexisme has quit [Ping timeout: 246 seconds]
<energizer>
i have defined a few modules that are just for me, and i'm wondering how i should install them. 1) home.packages = [(pkgs.callPackage ./modules/foo {})] 2) add { foo = pkgs.callPackage ./modules/foo {} } to the overlays list 3) something else?
<energizer>
i'm currently doing (1) and it works fine, just wondering if there's a better idea
romanofski has quit [Read error: Connection reset by peer]
romanofski has joined #home-manager
romanofski has quit [Read error: No route to host]
romanofski has joined #home-manager
romanofski has quit [Read error: Connection reset by peer]
romanofski has joined #home-manager
romanofski has quit [Read error: Connection reset by peer]
romanofski has joined #home-manager
romanofski has quit [Read error: Connection reset by peer]
romanofski has joined #home-manager
<rycee>
energizer: By "modules" you mean derivations, i.e., result of `mkDerivation`?
<rycee>
The term "module" is usually used for the NixOS module system, i.e., Nix functions producing an attribute set with `options` and `config` attributes.
__monty__ has joined #home-manager
<energizer>
rycee: ya derivations
<rycee>
Then either 1 or 2 is fine. The former is simpler but the latter is more convenient if you, for example, would like to publish your package in NUR later.
<rycee>
So I guess 3 would be setting up your own NUR and defining your package there. Then other people could also make use of the package. This assumes the package is of public interest, of course. Don't put packages that contains secret keys and such in NUR ;-)
malSet has quit [Read error: Connection reset by peer]
malSet has joined #home-manager
malSet has quit [Read error: Connection reset by peer]
malSet has joined #home-manager
mexisme has joined #home-manager
mexisme has quit [Ping timeout: 265 seconds]
cole-h has joined #home-manager
mexisme has joined #home-manager
mexisme has quit [Ping timeout: 260 seconds]
s1341 has quit [Quit: Connection closed for inactivity]
cole-h has quit [Ping timeout: 256 seconds]
hax404 has quit [Quit: WeeChat 2.7.1]
hax404 has joined #home-manager
cole-h has joined #home-manager
cole-h has quit [Client Quit]
cole-h has joined #home-manager
mexisme has joined #home-manager
mexisme has quit [Ping timeout: 246 seconds]
zeta_0 has joined #home-manager
mexisme has joined #home-manager
cole-h has quit [Ping timeout: 265 seconds]
zeta_0 has quit [Quit: rcirc on GNU Emacs 26.3]
cole-h has joined #home-manager
__monty__ has quit [Quit: leaving]
<cole-h>
rycee: The recent "non-NixOS helper" merge seems to have broken things for me. Still investigating.
<cole-h>
Or maybe not... Please hold.
<cole-h>
This is really weird. It happens when I update my `nixkpgs-wayland` checkout, but the only way to get sway to work again is by reverting the non-NixOS helper commit and switching to that...