| 28 Jul 2025 |
 emily | we don't want to add new activation scripts unless it's completely unavoidable | 17:32:13 |
| emily | (and moving stuff out of activation scripts is being worked on) | 17:32:36 |
| emily | (this doesn't necessarily determine where in the options hierarchy to put it though) | 17:34:06 |
 ElvishJerricco | It'll have to support systemd initrd if it's going to be upstreamed. The plan is to phase out scripted initrd over the next year or so, which means scripted-initrd-only things are not acceptable, though systemd-initrd-only things are acceptable. | 17:41:18 |
 magic_rb | Should be fine for ifstate, i run it not in the initrd but on systemd initrd | 17:44:03 |
| emily | ah I see it's already systemd.services.ifstate | 17:44:10 |
| emily | so never mind me about activation scripts | 17:44:16 |
| emily | I would personally probably go for services.ifstate.* IMO, it's comparable to services.network-manager.* in that you have a systemd service managing the config, but I'm ambivalent | 17:44:54 |
