<thomashoneyman>
...actually, i think i know what to do
<thomashoneyman>
i had to import the package with `fetchTarball` in the first place, then stick it in home.packages
<thomashoneyman>
so perhaps i can just refer to the package i put in home.packages directly
<thomashoneyman>
yes, looks like that's working
<thomashoneyman>
:rubber-duck
thomashoneyman has quit [Ping timeout: 245 seconds]
ryantrinkle has quit [Ping timeout: 248 seconds]
__monty__ has joined #home-manager
__monty__ has quit [Ping timeout: 245 seconds]
__monty__ has joined #home-manager
ardumont has quit [Quit: WeeChat 1.9.1]
ardumont has joined #home-manager
__monty__ has quit [Ping timeout: 245 seconds]
pie_ has quit [Ping timeout: 264 seconds]
<rycee>
Ryan is gone now but for future reference, the gnupg systemd service is socket activated, so it should start whenever something is attempting to connect to it.
<rycee>
pie_: Hmm, not certain why it causes an infinite recursion. Do you have the error with show-trace?
<rycee>
pie_: As an alternative, you could import the HM module from NUR: `imports = [ nur-no-pkgs.repos.rycee.modules.home-manager ];`
<rycee>
(which may or may not work better)
<alexarice[m]>
rycee: is nmd ready to use or is it's interface likely to change a lot at the moment?
<rycee>
Depends on your definition of "ready", I guess :-) It is still quite rough but in general the API seems to work quite well. I was, for example, able to add support for AsciiDoc files without having to change anything about the API.
<alexarice[m]>
I'm interested in using it for a project but will wait off on that if you thing there will be major changes to the way you use it
<alexarice[m]>
not so worried about missing features
<rycee>
If the current version works for you then I would suggest simply depending on a specific commit since then you don't have to worry about changin APIs.
<alexarice[m]>
rycee: thanks, I'll give that a go
<alexarice[m]>
rycee: thanks for the quick response as well
<rycee>
And I think there won't be any fundamental changes, at least for a while.
<rycee>
The main issue might be that there are some corner of the code that is not general enough for your use case. Only Home Manager is using nmd at the moment, as far as I know, so some pieces of nmd may be too hard coded for the HM manual. If you run into any such problem let me know and we'll see about fixing it.
<rycee>
My hope is that it'll become some reasonably easy framework to generate documentation for any project, in particular ones that use the NixOS module system.
<alexarice[m]>
rycee: thanks, I'll let you know how I get on, I'm mainly looking to make a list of configution options similar to `man home-configuration.nix` atm
<alexarice[m]>
rycee: I hadn't seen that but it does look quite similar, I'm attempting to try and make a whole distribution though at the moment it's more of an exercise for me to learn some elisp and nix
<rycee>
That sounds cool :-)
<rycee>
Yeah, my module is pretty bare-bones. Just a thin wrapper around use-package.
<alexarice[m]>
rycee: have just seen you used the defaultText attribute (which I wasn't aware of) to get round one of the problems I was having so I might be able to close a couple of the issues I made
<rycee>
Yeah, I wrote comments on the issues.
<rycee>
Two of them I think can be resolved by using `defaultText`.
<rycee>
The first one is quite valid, though.
<alexarice[m]>
ah yes, I've just seen
<alexarice[m]>
thanks for the info
romanofski has quit [Quit: ZNC 1.6.6 - http://znc.in]
romanofski has joined #home-manager
romanofski has quit [Quit: ZNC 1.6.6 - http://znc.in]
romanofski has joined #home-manager
<bsima>
i'd like to pin nixpkgs in home-manager, so i'm always using the same packages
<bsima>
i know how to do this is nixos, but how do i do it in home-manager?
<rycee>
You can try `_module.args.pkgs = mkForce (import …);
<bsima>
_module? so it's a per-module setting? i was thinking there should be a global way to do it
<rycee>
Hmm, what do you mean by "global"? The `_module.args.pkgs = …` thing should affect all modules loaded by HM.