<acowley>
I was just reinstalling nix on a macOS machine where something had gone wrong, and ran into the confusion about the root user having a channel subscription though nix-channel doesn't work normally with sudo. Is there a reason to have this subscription done through root rather than the user installing nix?
<gchristensen>
it is a confusing thing I agree :/
<acowley>
Even as someone fairly saturated in nix, I felt on very uncertain ground following the installation
<acowley>
gchristensen: Is there any downside to removing the channel from the root user and adding one as a regular user?
<gchristensen>
don't think so
<acowley>
The main reason why that seems preferrable is to make nix-channel usage more ergonomic than requiring `sudo -i su root` to work with it
<gchristensen>
yeah
<gchristensen>
by default, the question becomes whose channel does nix come from?
<gchristensen>
and the default profile becomes complicated
<acowley>
gchristensen: Why wouldn't it come from the user's channel subscription?
<gchristensen>
which user?
<acowley>
gchristensen: Is it that the nixbld users need to use nix?
<acowley>
gchristensen: The user running the installer
<gchristensen>
yeah, so that is a possible answer
<acowley>
Oh, and I apologized for the tangent here, but I was helping someone working through the nix pills series when they ran into things in the series not working on darwin. Is there a convenient way to offer some sort of commentary to those articles to indicate adaptations for darwin?
<acowley>
I'm imagining a kind of side bar or something
<gchristensen>
the source for them are on github if that works?
<gchristensen>
not sure if a sidebar is easy, but a note paragraph near the beginning would be good i agree
<acowley>
docbook has a sidebar element
<acowley>
Now I need to figure out if rendering the documents is something I can reasonable do
<acowley>
to make sure my changes look okay
<acowley>
The nice(st) thing about working on nix things is when they include build instructions
<gchristensen>
:) do the pills?
<acowley>
They do, and the build worked flawlessly
<acowley>
The sidebar element isn't styled in a helpful way unfortunately
<acowley>
I'll see about tweaking that
<gchristensen>
yay! glad to hear that is true
<gchristensen>
styling the sidebar is Complicated
<gchristensen>
because the local CSS doesn't necessarily match the prod CSS I think
<gchristensen>
:?
alexteves has quit [Remote host closed the connection]
jrolfs has joined #nix-darwin
<acowley>
I did what I could. It turns out there was already an open PR to fix this properly, but it made everything a bit too complicated, and so wasn't well-received. We'll see if folks prefer this light touch approach.
<acowley>
It's nice that it was very easy for me to do, so no harm if it's not wanted.
<gchristensen>
that is so good to hear, acowley :)
andreabedini has joined #nix-darwin
andreabedini has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<gchristensen>
it should upgrade the website on the next increment of 20min, ie: 21:40EDT
<acowley>
Whoa!
<acowley>
The idea of making that change only came as a whim when I was having my own unrelated nix-on-darwin struggles this afternoon. Thanks for making it move so fast, gchristensen!
andreabedini has joined #nix-darwin
<gchristensen>
aw shucks, I just pushed the merge button :)
<LnL>
like I mentioned before I think we shouldn't over complicate the pills
<gchristensen>
I agree
<LnL>
but hopefully this is succinct enough not to avoid people while getting the message across
<LnL>
s/avoid/confuse/
<LnL>
definitively better than nothing given all of the 'doesn't work on darwin' issues
<acowley>
LnL: Yeah, I didn't want to inject a choose your own adventure branching structure, but aimed to throw a lifeline out there.
<gchristensen>
acowley: : I wonder if <note> would be better than <sidebar> since we do render that uniquely
<acowley>
gchristensen: Sure! It renders the code in italics, which isn't ideal, but otherwise it fits the need quite well.
<LnL>
yeah exactly, if we put the stdenv implementation in the examples it would work, but nobody wants that :p
<gchristensen>
seems easier to fix than making a real sidebar in the CSS (unless samueldr wants to tackle that?)
<acowley>
What's going on with the style.css file, btw?
<gchristensen>
you mean dev vs. prod?
<acowley>
gchristensen: yes
<gchristensen>
the code emitted by docbook is processed by xslt, to add the nixos.org treatment, and then a new style.css is applied
<gchristensen>
it'd be nice to have it emit it directly but that is a bit complicated
<acowley>
The prod css is generated by docbook? There must be a way of influencing that generation, but I didn't find anywhere else that looked like custom XSLT or anything.
<gchristensen>
no
<gchristensen>
sorry, hands tired so a bit short on words
<acowley>
My next public relations PR will probably be to the main nixpkgs page at https://nixos.org/nixpkgs because I think it's not as welcoming as it could be.
<gchristensen>
I wonder if I could get away with running 2 copies of macOS in VMs if I physically put the machine running macOS _on top of_ apple hardware
<qyliss^work>
I just realised that gchristensen = grahamc hehe
<gchristensen>
:)
trcc has quit []
alexteves has joined #nix-darwin
stqism has quit [Quit: Like 3 fire emojis lit rn 🔥🔥🔥]
ryanartecona has joined #nix-darwin
ryanartecona has quit [Remote host closed the connection]
<cransom>
once upon a time i looked at virtualizing macos and iirc, they didn't care about the number of vms as long as the host the vmw as running on was apple hardware.
__Sander__ has quit [Quit: Konversation terminated!]
<gchristensen>
I have a shell.nix where when I run nix-shell, my computer shuts off
<cransom>
rube goldberg esque useless box?
<gchristensen>
lol
johnw has joined #nix-darwin
jrolfs has joined #nix-darwin
jrolfs has quit [Ping timeout: 240 seconds]
<johnw>
LnL: what does the speedFactor mean? Is 2 faster or slower than 1?
<gchristensen>
I believe so
<johnw>
haha, faster OR slower
flokli has quit [Quit: WeeChat 2.0.1]
<gchristensen>
faster :)
flokli has joined #nix-darwin
jrolfs has joined #nix-darwin
pikajude has quit [Remote host closed the connection]
pikajude has joined #nix-darwin
pikajude has quit [Remote host closed the connection]
pikajude has joined #nix-darwin
jrolfs has quit [Ping timeout: 276 seconds]
rizary has quit [*.net *.split]
jrolfs has joined #nix-darwin
jrolfs has quit [Ping timeout: 240 seconds]
cstrahan_ has quit [*.net *.split]
mightybyte has quit [*.net *.split]
mightybyte has joined #nix-darwin
jtojnar has joined #nix-darwin
cbarrett_ has joined #nix-darwin
sphalerite_ has joined #nix-darwin
<dhess>
LnL: is there a nix-darwin setting for the nix.conf tarball-ttl setting?
<LnL>
not an option, use nix.extraOptions = '' tarball-ttl = 1 '';
<dhess>
oh cool, thank you
sphalerite has quit [*.net *.split]
hamishmack has quit [*.net *.split]
cbarrett has quit [*.net *.split]
gchristensen has quit [*.net *.split]
cbarrett_ is now known as cbarrett
<dhess>
I don't get that option. Why would I want my tarballs to expire?
<LnL>
impure urls
<LnL>
like builtins.fetchGit of master that automatically updates
<dhess>
ugh
gchristensen has joined #nix-darwin
jrolfs has joined #nix-darwin
<cransom>
i have a `base.nix` that i import in many configs for some shared configuration that i update sometimes more frequently than the default tarball-ttl.
<dhess>
cransom: isn't tarball-ttl just for fetchTarball?
<cransom>
no, it applies for fetchGit/fetchurl as well.
<cransom>
i don't know if it's officially true, but i consider anything that i don't give a sha256 output for, to fall under that tarball-ttl
<LnL>
_tarball_-ttl obviously also applies to git :p
<LnL>
yeah, the option doesn't really have anything to do with tarballs
<dhess>
that's even worse
<dhess>
ffffuuuuuuu
<LnL>
what's the problem?
<dhess>
no wonder my builds were fetching things after I'd already built them.
<LnL>
(except the bad option name)
<dhess>
LnL: If you go to the trouble of making sure a project builds so that you can work on it offline, and suddenly Nix decides that it wants to download tarballs again, you're gonna have a bad time.
<LnL>
how's that related
<LnL>
tarball-ttl only affects things without hashes, which are inherently not properly cachable
<dhess>
The Nix manual doesn't make that distinction. Or if it does, it's not very clear.
<dhess>
And if it applies to fetchGit then you must be incorrect, no? Because there is no way to do fetchGit without a hash.
<dhess>
oh maybe there is, never mind
<dhess>
Anyway, the manual is not clear on any of this, especially the fact that it applies to more than fetchTarball.
<LnL>
builtin.fetch* can be used eval time without a hash
jrolfs has quit [Ping timeout: 264 seconds]
<johnw>
LnL: so, it looks like even though I have a 10 core machine that's much, much faster than either of my laptops, the distributed build wants to only use the laptops 95% of the time
<johnw>
if I can get it to prefer the desktop, it's actually not even worth distributing these builds
<johnw>
can't get*
<johnw>
it's only building on the slowest machines I have
rizary has joined #nix-darwin
jrolfs has joined #nix-darwin
jrolfs has quit [Ping timeout: 268 seconds]
alexteves has quit [Remote host closed the connection]