<nostate>
johnw: Oh, do you clone that nix-config repo into your home directory?
<johnw>
I rsync ~/src to the new machine
<johnw>
I use config/bootstrap.nix, which is a pared down version of darwin.nix
<johnw>
then, once Nix is partway there
<johnw>
I nix copy over the closure of my full environment
<johnw>
like sourdough starter, this all depends on an existing, working machine
<johnw>
(which has always been the case)
<nostate>
lol
<johnw>
I haven't truly "started out cold" in decades
<nostate>
I'm trying to figure out how to set these things up so I can do something really simple like cloning a repo and running a script to get everything off to the races.
<johnw>
ah, I've never tried to achieve a true bootstrap capability
<johnw>
the very first thing I do after installing a new OS on a new machine is to rsync over all of my "data"
<nostate>
If my machine disappears, I want to be able to be up and running quickly.
jtojnar has quit [Remote host closed the connection]
<johnw>
and then I install Nix, install nix-darwin, setup NIX_PATH, run bootstrap.nix, nix copy, and then run the full darwin.nix
<johnw>
I have multiple machines, multiple backups
<johnw>
I don't try to accomodate a situation of "no backup"
<johnw>
accommodate
jtojnar has joined #nix-darwin
<nostate>
Do you hava any ideas about my question above getting home manager to work with: ".tmux.conf".source = ./tmux.conf;
<nostate>
That combined with the inside items not being indented was why I glossed over it.
<pikajude>
man, i am really tempted to start using cabal new-build over nix
<nostate>
pikajude: Oh? Why's that?
<pikajude>
nix is locked into a specific version of every hackage package and you have to maintain a manual overrides list
<nostate>
pikajude: Ahh, yeah.
<pikajude>
the benefits of nix used to be you could toggle profiling on/off, maintain different package sets easily, etc.
<pikajude>
plus jailbreaking
<pikajude>
but with cabal you can set allow-newer for packages, new-build puts different build configs in different directories
<pikajude>
also specifically for this project, I can use the head.hackage.haskell.org repo if i'm using real cabal-install
<nostate>
Yeah, I've used new-build recently. It was a pretty good experience.
nostate has quit [Ping timeout: 260 seconds]
<pikajude>
i don't remember if you could repl a test target with old cabal, but you can now
nostate has joined #nix-darwin
nostate has quit [Ping timeout: 252 seconds]
nostate has joined #nix-darwin
nostate has quit [Client Quit]
<pikajude>
only real issue is that the new solver is preposterously slow and the solver reruns after any cabal file change, even if you just exposed a new module or added a compiler option