angerman changed the topic of #haskell.nix to: https://input-output-hk.github.io/haskell.nix - alternative haskell infrastructure for nix; logs at https://logs.nix.samueldr.com/haskell.nix
srk has quit [Ping timeout: 268 seconds]
srk has joined #haskell.nix
srk has quit [Ping timeout: 268 seconds]
srk has joined #haskell.nix
strikerlulu has quit [Ping timeout: 240 seconds]
hekkaidekapus_ has quit [Ping timeout: 268 seconds]
hekkaidekapus_ has joined #haskell.nix
<michaelpj> jlode: hmm, I've seen that one bite multiple people, I should probably add it to the troubleshooting section
fendor has joined #haskell.nix
<ocharles> Yea, I added a tip about that to our internal work documentation on setting up our private cache
<ocharles> It got me!
fendor_ has joined #haskell.nix
fendor has quit [Ping timeout: 240 seconds]
srk has quit [Remote host closed the connection]
srk has joined #haskell.nix
__monty__ has joined #haskell.nix
<DigitalKiwi> why is there not a way to make the cache directives a part of the project
<DigitalKiwi> (or is there i'm not aware of)
<__monty__> DigitalKiwi: Because caches imply trust.
<DigitalKiwi> well if i'm compiling something i download off of github; if i can't trust them with a cache how can i trust their code? and half the time the instructions are `cachix use` anyway
<__monty__> So I haven't progressed on the cross-compiling issue from yesterday. As ocharles pointed out, this line (https://github.com/toonn/taskell/runs/1846286706?check_suite_focus=true#step:5:16615) is missing a `--dependency=terminfo=blah` argument. What is the next step in digging into this? Is this command generated by haskell.nix or cabal?
<__monty__> DigitalKiwi: Trusting code v. binaries are different levels of trust. I also wouldn't like projects messing with my nixpkgs.config, so that leaves projects managing their own cache which sounds like herding cats. More magic means less control. It's not as if adding a binary cache when you want to is hard.
<__monty__> Both the project and nix itself are also still in flux so IMO it's understandable UX isn't the highest priority yet.
<DigitalKiwi> nixos is 18 years old
<DigitalKiwi> it's older than fedora
<DigitalKiwi> though having red hat behind it probably gives it some advantage :)
hekkaidekapus{ has joined #haskell.nix
hekkaidekapus_ has quit [Ping timeout: 268 seconds]
ocharles has quit [Ping timeout: 240 seconds]
feepo has quit [Ping timeout: 265 seconds]
lally has quit [Ping timeout: 265 seconds]
tnks has quit [Read error: Connection reset by peer]
mpickering has quit [Read error: Connection reset by peer]
gluegadget has quit [Read error: Connection reset by peer]
dmj` has joined #haskell.nix
lally has joined #haskell.nix
joshmeredith has joined #haskell.nix
ajmcmiddlin has joined #haskell.nix
ocharles has joined #haskell.nix
jbetz has joined #haskell.nix
adamse has joined #haskell.nix
buggymcbugfix has joined #haskell.nix
mpickering has joined #haskell.nix
Tritlo has joined #haskell.nix
feepo has joined #haskell.nix
tnks has joined #haskell.nix
hamishmack has joined #haskell.nix
gluegadget has joined #haskell.nix
<ocharles> __monty__: I do think a project should be able to say "I want to use these caches", and trust can be configured elsewhere. So If I haven't trusted the cache, Nix can say "whoops, I wanted to use this cache but you don't trust it. Continuing without using it"
<ocharles> Much more explainable than putting a note in a README
<__monty__> Sure but like I said haskell.nix is quite new still. I understand the focus is on their business use case first and the wider community second.
<__monty__> DigitalKiwi: Haskell.nix is only a year or maybe two old by this point, certainly not older than Fedora.
<DigitalKiwi> i wasn't talking about haskell.nix i meant nix in general
<__monty__> Afaict flakes is a step towards linking caches to projects.
hekkaidekapus{ has quit [Ping timeout: 268 seconds]
hekkaidekapus{ has joined #haskell.nix
proofofkeags has joined #haskell.nix
strikerlulu has joined #haskell.nix
fendor_ is now known as fendor
hamishmack has quit [Ping timeout: 264 seconds]
mpickering has quit [Ping timeout: 272 seconds]
Tritlo has quit [Read error: Connection reset by peer]
dmj` has quit [Read error: Connection reset by peer]
hamishmack has joined #haskell.nix
dmj` has joined #haskell.nix
Tritlo has joined #haskell.nix
mpickering has joined #haskell.nix
o1lo01ol1o has quit [Remote host closed the connection]
srk has quit [Remote host closed the connection]
srk has joined #haskell.nix
{`-`} has joined #haskell.nix
o1lo01ol1o has joined #haskell.nix
o1lo01ol1o has quit [Ping timeout: 240 seconds]
o1lo01ol1o has joined #haskell.nix
julm has quit [Remote host closed the connection]
julm has joined #haskell.nix
julm has quit [Remote host closed the connection]
julm has joined #haskell.nix
proofofkeags has quit [Ping timeout: 272 seconds]
fendor has quit [Remote host closed the connection]
proofofkeags has joined #haskell.nix
fendor has joined #haskell.nix
<infinisil> ocharles: DigitalKiwi: Nix actually has that feature now! https://github.com/NixOS/nix/pull/4189
<__monty__> Looks like they don't deal with the trust issue yet?
feepo has quit [Ping timeout: 246 seconds]
feepo has joined #haskell.nix
<ocharles> Neat
<DigitalKiwi> infinisil: nice finally something i like about flakes
<DigitalKiwi> that's exactly what i wanted to be able to do
<infinisil> __monty__: Nowadays it asks you interactively whether you want to trust it
<__monty__> Ah, cool. Does come with a risk of bad press for NixOS when a malicious cache pops up though.
aveltras has joined #haskell.nix
__monty__ has quit [Quit: leaving]
fendor has quit [Read error: Connection reset by peer]