supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
dhess has quit [Remote host closed the connection]
m1cr0man has joined #nixos-dev
cole-h has joined #nixos-dev
ris has quit [Ping timeout: 256 seconds]
<hexa->
supersandro2000: your EOL message could use a more friendly tone
<hexa->
please thank the respecitve author for their contribution and explain that due to $issues it couldn't be merged in time and unfortunately 20.03 is now EOL.
<hexa->
:)
<hexa->
other than that, thanks for taking care of closing stuff
<infinisil>
Btw github has a "saved replies" feature, where you can save replies for easy reuse
<infinisil>
Also, you can search for "base:release-20.03 is:open" to find any remaining 20.03 PRs :)
<infinisil>
Also, supersandro2000++ for banging out those reviews and merges recently!
<{^_^}>
supersandro2000's karma got increased to 16
<hexa->
indeed, totally worth it
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-dev
orivej has joined #nixos-dev
<supersandro2000>
hexa-: I can't copy this message like it is?
<supersandro2000>
also the two PRs where backports which do not matter anymore.
<supersandro2000>
infinisil: I am not closing all of them. I just stumbled over two very old and thought why not.
<supersandro2000>
the mass close should be done by someone with a script or I go crazy
<supersandro2000>
there are 5 more... lol
<supersandro2000>
closed them with a friendly comment :)
<hexa->
supersandro2000: copy which message?
<hexa->
your latest message sounds totally fine
abathur has quit [Quit: abathur]
marek has quit [Ping timeout: 260 seconds]
abathur has joined #nixos-dev
marek has joined #nixos-dev
<supersandro2000>
> due to $issues it couldn't be merged in time and unfortunately 20.03 is now EOL.
<{^_^}>
error: syntax error, unexpected $undefined, expecting ')', at (string):437:8
<hexa->
copy whatever you like
<supersandro2000>
I mean with $issue
<supersandro2000>
not swapping it out
alp has joined #nixos-dev
<Ericson2314>
lopsided98: I'm trying to gauge whether I have time to embark on the journey to the holly grail of buildRustCrate-ing rustc and the standard library (the latter via -X build-std) :)
<Ericson2314>
I think I mentioned that to you before?
cole-h has quit [Ping timeout: 246 seconds]
<lopsided98>
Yes, I think that's a great idea.
<lopsided98>
I'd be glad to review anything you work on, but I'm not planning to start on it myself in the near future.
<lopsided98>
Ericson2314: Although I'd think the biggest benefit would come from just focusing on std so we can support multiple targets with one rustc. It seems like using buildRustCrate for all of rustc might just be a bigger maintenance burden.
<Ericson2314>
lopsided98: that's a good point
<Ericson2314>
But also I think buildRustCrate for rustc will be comparatively easy 🙂
<lopsided98>
Ok, I'm not really familiar with the rustc build process. I was just thinking that there seemed to be a lot of crates involved :)
<Ericson2314>
lopsided98: well a lot of crates, but i don't think any funny IO or other externalities
<Ericson2314>
except for maybe the ones linking LLVM
<Ericson2314>
but there's always cranelift
<lopsided98>
Would you use crate2nix, or do it all by hand?
<Ericson2314>
lopsided98: crate2nix
<Ericson2314>
i think that's the way to justify the maintainability
<lopsided98>
Ericson2314: ok, yeah, that shouldn't be too hard to maintain
alp has quit [Ping timeout: 272 seconds]
<Ericson2314>
fingers crossed!
<samueldr>
[01:49:12] <supersandro2000> is it cool to just revert a commit to fix a package or should I do it as a part of a package upgrade?
<samueldr>
there is no straight unambiguous answer
<MichaelRaskin>
By now I have no idea what the goal of the docs is, as any discussions of purpose are structure have been moved aside to finish the format transition to better support the unstated goals of docs
<lukegb>
haha
<infinisil>
I'm kind of hoping we can just wipe the docs and restart fresh, with clear goals
<infinisil>
Of course, ain't nobody got time for that though
<MichaelRaskin>
I would prefer resetting Nix to the state currently documented by the Nix manual
<infinisil>
Hehe
<infinisil>
Are flakes documented?
<MichaelRaskin>
Definitely not well
<lukegb>
They shouldn't be, they're experimental! *bonk*
<siraben>
I would use flakes if they were documented more
<MichaelRaskin>
It is unclear to me why _this_ behaves like it does from Nix manual, so let's roll back to before that mess and follow the crrent manual
<siraben>
Even after seeing Eelco's talk and others, it's not totally clear
<infinisil>
MichaelRaskin: "access to path '/home/infinisil/test/direct/direct.nix' is forbidden in restricted mode"?
<MichaelRaskin>
Yes
<infinisil>
Ah yeah, that's pure eval mode, you can't access arbitrary paths anymore
<{^_^}>
pypa/packaging#363 (by ahesford, 9 hours ago, open): Reliance on flit makes packaging incompatible with Void, Arch and Alpine Linux package systems
<infinisil>
If I were to create a label for PR's that are interesting or novel, what name would you give that label? Some examples of PR's that would be labeled with it: #105319 #101127 #87661 #91724
<ryantm>
Please self nominate as shepherd for https://github.com/NixOS/rfcs/pull/80 we want to get it through as quickly as is reasonable so we can minimize uncertainty.