| 9 Mar 2025 |
 aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | Then you have to bind to it unless you want to break compatibility | 17:24:56 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | And there are platform assumptions downstream so we can't just ship what we want by default, like clang 😅 | 17:26:36 |
 Sergei Zimmerman (xokdvium) | IMO just using standard C++ regex is already is the wrong decision. It’s notorious for poor performance. CTRE and Boost.Regex is much better in that regard. Though regex in any systems programming language smell.
That reminds me of https://regexlicensing.org/ | 18:44:10 |
 Qyriad | Redacted or Malformed Event | 20:00:57 |
| Qyriad | (Wait wrong channel sorry) | 20:01:35 |
| 10 Mar 2025 |
 connor (burnt/out) (UTC-8) | Randy Eckenrode: would you happen to know if darwin uses an out-of-the-ordinary shell with respect to Nixpkgs builds? Put another way, do darwin systems use their host machine's bash, an old/vendored version of bash, or the same version linux machines would?
I ask because I'm making setup hooks which use some bash-isms, and I see comments littered throughout Nixpkgs about hacking around old versions of bash for darwin. | 17:04:57 |
 K900 | Should be standard nixpkgs bash | 17:07:15 |
| K900 | Minus platform specific sheet | 17:07:25 |
| K900 | * Minus platform specific shit | 17:07:26 |
| K900 | (see above) | 17:07:28 |
 Randy Eckenrode | In reply to @connorbaker:matrix.org
Randy Eckenrode: would you happen to know if darwin uses an out-of-the-ordinary shell with respect to Nixpkgs builds? Put another way, do darwin systems use their host machine's bash, an old/vendored version of bash, or the same version linux machines would?
I ask because I'm making setup hooks which use some bash-isms, and I see comments littered throughout Nixpkgs about hacking around old versions of bash for darwin. Darwin uses nixpkgs Bash (whether from the bootstrap tools or freshly built).
How old are those comments? Darwin may have used the system when it had a native (impure) toolchain, but that was a decade ago.
The only exception that comes to mind is a foopkg-config script from when patchShebangs wasn’t available, but I’m pretty sure I fixed that during the Clang 16 update.
| 17:08:52 |
| connor (burnt/out) (UTC-8) | Some of them are from about a decade ago haha | 17:09:19 |
| Randy Eckenrode | Redacted or Malformed Event | 17:11:33 |
 emily | kill 'em | 19:04:48 |
| emily | it's just old cruft | 19:04:52 |
| 12 Mar 2025 |
|  vidariondr joined the room. | 21:08:50 |
| 14 Mar 2025 |
 Tristan Ross | We've got a bunch of PR's and we should make progress on them. I'm thinking we can probably do:
- Create a project board on GH
- Meet regularly to discuss PR's and the current plan for the stdenv
| 17:44:42 |
| Tristan Ross | I've made a board https://github.com/orgs/NixOS/projects/92/views/1 | 18:11:51 |
| Tristan Ross | Had to rebase https://github.com/NixOS/nixpkgs/pull/365057 again. Let's get this reviewed and merged soon. Every time I rebase, it makes looking for previous reviews difficult. | 18:23:39 |
| 17 Mar 2025 |
| Tristan Ross | This Thursday (2025-03-20) @ 9am - 10am PST will be the first meeting. I hope this will allow us to have a more coordinated effort towards development.
Goals:
- Meet & greet
- Determine overall plan (+ 25.05)
- Highlight work done since Oct
Link: https://jitsi.lassul.us/nixpkgs-stdenv
| 02:40:12 |
| emily | I won't have time to do a full re-review before next weekend-ish but fwiw the last time I glanced at this there were review comments I left last time that hadn't been addressed | 04:07:29 |
| emily | also like I said the easy way to land this without needing rebase/review of a huge monolithic PR is to split it up as read-only → convert existing users of useLLVM gradually → hook them up to bootstrap → make them writable and deprecate useLLVM | 04:08:22 |
| Tristan Ross | In reply to @emilazy:matrix.org
I won't have time to do a full re-review before next weekend-ish but fwiw the last time I glanced at this there were review comments I left last time that hadn't been addressed Oh ok, idk what could be missing | 04:23:54 |
| Tristan Ross | In reply to @emilazy:matrix.org
also like I said the easy way to land this without needing rebase/review of a huge monolithic PR is to split it up as read-only → convert existing users of useLLVM gradually → hook them up to bootstrap → make them writable and deprecate useLLVM Oh, I didn't realize that's what you meant. | 04:24:06 |
| emily | I think https://github.com/NixOS/nixpkgs/pull/365057#discussion_r1927841995 wasn't addressed? but like I said I haven't had time to go over the whole thing again
btw, there is overlap with https://github.com/NixOS/nixpkgs/pull/352629, so we'll need to decide what we want to do there
| 04:29:00 |
| Tristan Ross | I think the has in cases of multiple possible variants will just cause issues. | 05:09:41 |
| Tristan Ross | I think I did address that or mostly did. | 05:10:31 |
| emily | ah, I see the assert now. that might work. the premature warnings are still there though. but I'll try to take a closer look next weekend | 05:31:06 |
| Tristan Ross | I'm not sure how to handle the warnings since I don't think there's much of a delay between this PR coming and 25.05. | 05:36:45 |
| emily | they shouldn't be deprecated/warned until we have replacements that are hooked up to bootstrap properly. it doesn't make sense to deprecate parameters before setting their replacements works properly | 05:53:01 |
