Nixpkgs Stdenv | 225 Members | |
| 74 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Dec 2024 | ||
In reply to @philiptaron:matrix.orgSounds good | 21:48:30 | |
| I'm thinking we can do a meeting sometime after the new year so we can figure things out for what the SC wants. | 21:50:31 | |
| The sad (but also great) fact of the matter is that I'm most available over the next couple weeks, since I'm off of work. | 21:57:53 | |
| Posted: https://discourse.nixos.org/t/community-team-updates/56458/11?u=philiptaron | 21:58:56 | |
| Oh | 22:02:36 | |
| Yeah, I'm available on Tuesday to Thursday this week | 22:03:56 | |
In reply to @philiptaron:matrix.orgI thought you were meaning a different discourse post lol | 22:04:12 | |
| 😬 | 22:04:42 | |
| It's fine lol | 22:07:04 | |
| I kept "who authored this" in there, so that if there's "hell no we aren't doing that" it would be clear where the stones ought to be thrown. Don't expect that, though. | 22:08:11 | |
| Yeah lol | 22:08:42 | |
| 22 Dec 2024 | ||
| There's a few things that I've been thinking of:
| 04:27:06 | |
| * There's a few things that I've been thinking of:
| 04:27:57 | |
| My $0.02 is that I'd definitely use option #2, especially when doing cross compiles | 04:29:20 | |
Yeah, #2 is something which I've been trying to work on for some time. I had a PR which adds a cpuModel attribute that is capable of it but it's been sitting stale from little to no reviews and constantly getting blocked with merge conflicts. | 04:31:32 | |
| I likely would start fresh for doing #2 and drop the CPU model PR I originally made. Hopefully people could review that one and we could actually get it. | 04:32:10 | |
| #3 and #4 are kinda big since it likely would break a lot. Might not be bad to work on those later on and do it right after a release when things are fixed. | 04:33:10 | |
| #1 is more about educating more and it's more of a preferences things and down to how Nix is "taught/learned". | 04:33:38 | |
| Fun, think I've found a case where gettext fails to build with symptoms like this: https://trac.macports.org/ticket/44387 But only if NIX_DEBUG is set. Presumably because there is some kind of build system race. I'm managing to trigger it with flto (fat objects) switched on with clang. Turning off NIX_DEBUG seems enough to make it work reliably (at least haven't observed the failure case). | 11:50:23 | |
| 13:25:19 | ||
In reply to @rosscomputerguy:matrix.orgI’ve been advocating it, but I don’t think it was my idea. Maybe @emilazy:matrix.org? | 14:11:51 | |
| 15:55:33 | ||
In reply to @reckenrode:matrix.orgOh ok, I only know about it from you. | 18:12:07 | |
| It's probably something we can definitely do but a bit down the road. Likely would break a lot of things. | 18:12:55 | |
| 23 Dec 2024 | ||
| Being explicit about your build system would definitely be a big and breaking change. | 00:01:21 | |
| It's worth doing, even it it might mean moving away from the "stdenv" name. | 14:37:05 | |
| I was thinking about this, I really like what the conan package manager has done in this area. Basically keep a c/c++ "model" then translate into build-tool native integrations (eg toolchain files for cmake) | 16:21:52 | |
| Conan's model is very complete and takes cross compilation into account | 16:22:46 | |
In reply to @philiptaron:matrix.orgMaybe, I'm 50/50 on that. | 16:42:05 | |
| 25 Dec 2024 | ||
In reply to @k900:0upti.meWe have bare metal targets despite few things building | 17:32:50 | |