# 2025-09-17 Nix team meeting minutes #248

**URL:** https://discourse.nixos.org/t/2025-09-17-nix-team-meeting-minutes-248/69508
**Category:** Nix
**Created:** [September 17, 2025, 8:52pm UTC](https://discourse.nixos.org/t/2025-09-17-nix-team-meeting-minutes-248/69508 "2025-09-17T20:52:24Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![roberth](https://discourse.nixos.org/user_avatar/discourse.nixos.org/roberth/32/5488_2.png) [@roberth](https://discourse.nixos.org/u/roberth)
#### Post date: [September 17, 2025, 8:52pm UTC](https://discourse.nixos.org/t/2025-09-17-nix-team-meeting-minutes-248/69508/1 "2025-09-17T20:52:24Z")

</div>

In the meanwhile, we’ve had some triage meetings whose outcomes were posted on the issues/prs, as well as some hacking sessions without notes.

# 2025-09-17 Nix team meeting minutes #248

_Wednesday triage meeting_

Attendees: @edolstra @xokdvium @roberth @Ericson2314

## Triage

### [Use `MemorySourceAccessor` in `DummyStore` so writes work by Ericson2314 · Pull Request #10915 · NixOS/nix · GitHub](https://github.com/NixOS/nix/pull/10915)

Merged

### [Multiple `--apply` flags · Issue #13898 · NixOS/nix · GitHub](https://github.com/NixOS/nix/issues/13898)

Idea approved

### [Feature Request: `--apply` option for `nix build` command · Issue #11698 · NixOS/nix · GitHub](https://github.com/NixOS/nix/issues/11698)

Discussed

### [[F.Rq.] Option to apply stricter scoping rules during eval · Issue #13214 · NixOS/nix · GitHub](https://github.com/NixOS/nix/issues/13214)

Closed as not planned

### [Add a warning infrastructure · Issue #10281 · NixOS/nix · GitHub](https://github.com/NixOS/nix/issues/10281)

Idea approved

### [`builtin:write-file` · Issue #14011 · NixOS/nix · GitHub](https://github.com/NixOS/nix/issues/14011)

Opened and discussed

### Stack traces for warnings

@Mic92: In Nixpkgs we have trouble getting locations for warnings  
@xokdvium: A consequence of our error handling architecture  
@roberth: Piggy-back on the debugger mechanism? That does track the stack without having to unwind. Should be a new flag that enables the debugger mechanism but not necessarily the debugger.