<
matthewcroughan>
I'm looking at this, wondering how exactly I can have my own "dailydriver"
<
matthewcroughan>
Oh, nvm, I see what's going on there now.
<
matthewcroughan>
Daily driver is defined in 11
<
matthewcroughan>
But, if I wanted to load a file instead of an attrset, how would I do it?
<
danielrf[m]>
Yep, should be like flakes for NixOS, except instead of the hostname by default, you can name it whatever you want
<
danielrf[m]>
Probably: robotnix.lib.robotnixSystem (import ./configuration.nix)
<
matthewcroughan>
Can you have multiple flakes in a repo?
<
matthewcroughan>
Would you avoid that?
<
matthewcroughan>
Also, why would this go under defaultPackage.x86_64-linux ?
<
danielrf[m]>
Not sure if you can have multiple flakes in a repo
<
danielrf[m]>
I doubt it though
<
danielrf[m]>
The defaultPackage thing is entirely optional
<
matthewcroughan>
Is it arbitrary though?
<
matthewcroughan>
is that an arbitrary name? Or is it a special name
<
danielrf[m]>
defaultPackage is not arbitrary, but our use of it is
<
danielrf[m]>
defaultPackage is what gets built if you run `nix build` on the flake
<
danielrf[m]>
without any other options I mean
<
danielrf[m]>
The idea was to allow others to reproduce your exact configuration with something like `nix build github:owner/example`
<
matthewcroughan>
yeah I see.. hmm
<
matthewcroughan>
danielrf[m]: How could I make a list of robotnix systems?
<
matthewcroughan>
here's a little sketch of what I mean
<
matthewcroughan>
can I do robotnixConfigurations = with robotnix.lib.robotnixSystem?