| 1 Feb 2024 |
 @qyriad:matrix.org | I don't know about the others though | 00:32:35 |
 raitobezarius | I am aware of stdenv non derived by nixpkgs and those are completely different beast having their own semantics | 01:42:51 |
| raitobezarius | Before documenting what is a valid nixpkgs abiding stdenv, I think if we can document how to derive more complicated stdenv using combinators, that'd be great | 01:43:10 |
| raitobezarius | Documenting a valid nixpkgs abiding stdenv is bound to be very complicated notably due to splicing constraints, etc. which are not even totally clear for experts | 01:43:29 |
| @qyriad:matrix.org | In reply to @aliarokapis:matrix.org
I am not sure if that is the case with llvmPackages.stdenv and there are also some other stdenvs with other compilers both in stdenv and in various third party flakes. * LLVM's stdenvs are overrideCCs on base stdenv: https://github.com/NixOS/nixpkgs/blob/e4f711a40e2124d11f84c3e67443d02fa413a634/pkgs/development/compilers/llvm/16/default.nix#L319 | 02:05:09 |
 @jade_:matrix.org | In reply to @aliarokapis:matrix.org
Yea I mean compatible with mkDerivation and other nixpkgs assumptions like the isPlatform checks and others I'm very suspicious of if that's actually well defined at all, there's some extremely tight coupling, especially with respect to the (imo) pretty evil stuff stdenv does with security hardening flags | 02:41:41 |
 Alexandros Liarokapis | In reply to @raitobezarius:matrix.org
Documenting a valid nixpkgs abiding stdenv is bound to be very complicated notably due to splicing constraints, etc. which are not even totally clear for experts This is a very good note, my main usecase currently is to use standard industry toolchains for cross building so keeping derivations compatible with the cross building infra is important. | 12:47:25 |
| Alexandros Liarokapis | Using such external toolchains is sometimes required due to them being IEC 61508 qualified. | 12:53:33 |
| Alexandros Liarokapis | Which allows them to be used in automotive and similar sectors, so it is good to have an escape hatch to use your own stdenv. Nix would be a great pitch for such sectors due to facilitating reproducible builds but this is kind of a game breaker because verifying compilers is expensive. | 12:57:07 |
| raitobezarius | If this is your usecases, I'd build various checks to ascertain that no non IEC 61508 component is used and fail the evaluation if so | 12:59:20 |
| raitobezarius | Then you can build your compliant stdenv | 12:59:27 |
| Alexandros Liarokapis | My point is that it's kind of underspecified what consists of a valid stdenv. Ideally the custom stdenv is also compatible with the usual cross building infra which means proper splicing and derivations shouldn't need to change much at least for compatible components that are buildable with both stdenvs. But I know this whole thing is not trivial to even document. | 13:04:36 |
| 3 Feb 2024 |
|  raboof changed their display name from raboof to raboof @FOSDEM. | 07:38:34 |
 Philip Taron (UTC-8) | In reply to @infinisil:matrix.org
There is one remaining problem with the current pkgs/by-name check, and this fixes it: https://github.com/NixOS/nixpkgs/pull/285089
Quite a bit of Rust code there, would appreciate a review
Done. Many comments, but only a couple that I think are worthy of spending any work on. | 19:05:17 |
 infinisil | Philip Taron (UTC-8): Thanks a lot! | 20:17:58 |
| infinisil | I'll get to it next week :D | 20:18:11 |
| infinisil | (or maybe tomorrow) | 20:18:20 |
| Philip Taron (UTC-8) | In reply to @infinisil:matrix.org
(or maybe tomorrow) Sounds good | 21:09:16 |
| 4 Feb 2024 |
|  Bryan Honof changed their profile picture. | 11:31:18 |
| raboof changed their display name from raboof @FOSDEM to raboof. | 17:41:16 |
| 5 Feb 2024 |
 K900 | This is not quite a NAT issue, but I'm adding another top level package set in https://github.com/NixOS/nixpkgs/pull/286522 | 16:27:31 |
| K900 | Would appreciate some eyes on it | 16:27:53 |
| Philip Taron (UTC-8) | In reply to @infinisil:matrix.org
Philip Taron (UTC-8): Thanks a lot! ✅ after your updates. | 19:45:08 |
| infinisil | In reply to @philiptaron:matrix.org
✅ after your updates. 🚀 | 19:47:16 |
| Philip Taron (UTC-8) | You still have to pin the new version, right? | 19:47:58 |
| infinisil | Philip Taron (UTC-8): Yup | 19:50:25 |
| infinisil | Gotta wait for Hydra now | 19:50:30 |
| infinisil | Should really move that codebase to a separate repo, add some versioning on top and then rely on automatic bot updates to pin it in Nixpkgs | 19:51:02 |
| Philip Taron (UTC-8) | I think that'd be a good idea. | 19:51:38 |
| Philip Taron (UTC-8) | nixos/nixpkgs-ratchet? | 19:51:50 |
