| 7 Mar 2023 |
@elvishjerricco:matrix.org | So in order to use networkctl, you need dbus, as far as I can tell. | 02:27:53 |
@elvishjerricco:matrix.org | Ugh | 02:27:57 |
@elvishjerricco:matrix.org | But NixOS supports two different dbus implementations so that makes it trickier to implement that | 02:34:23 |
@lily:lily.flowers | In reply to @elvishjerricco:matrix.org But NixOS supports two different dbus implementations so that makes it trickier to implement that I mean, we could technically only support one for initrd, because it doesn't need to live past initrd, right? | 02:37:11 |
@elvishjerricco:matrix.org | Possibly. Just feels a little disingenuous to tell the user they've replaced dbus with broker, but then not do that in initrd :P | 02:37:55 |
@lily:lily.flowers | Yeah, that's fair | 02:38:42 |
@elvishjerricco:matrix.org | it also just feels weird to have dbus in initrd at all | 02:39:00 |
@elvishjerricco:matrix.org | I mean it'll be socket activated so the only cost will be size | 02:39:09 |
@elvishjerricco:matrix.org | but still | 02:39:13 |
@lily:lily.flowers | In reply to @elvishjerricco:matrix.org it also just feels weird to have dbus in initrd at all Yeah, it does a bit | 02:39:50 |
@lily:lily.flowers | In reply to @elvishjerricco:matrix.org I mean it'll be socket activated so the only cost will be size I imagine broker is much smaller if you only want to support one, though... | 02:39:59 |
@elvishjerricco:matrix.org | I imagine supporting either will be pretty minimal in terms of size | 02:40:22 |
@elvishjerricco:matrix.org | Well... I removed the dbus-daemon binary from the initrd and networkctl still worked... The dbus.service failed, but networkctl didn't seem to care? | 03:06:42 |
@elvishjerricco:matrix.org | wtf | 03:06:52 |
@elvishjerricco:matrix.org | oh, just networkctl status worked; nothing else seemed to | 03:11:09 |
@elvishjerricco:matrix.org | Finally marked this as ready for review: https://github.com/NixOS/nixpkgs/pull/169116 | 04:56:39 |
@elvishjerricco:matrix.org | It's slightly a hodgepodge of a bunch of little requirements to make everything work, so you might want to take it a commit at a time | 04:57:33 |
@andi:kack.it | That is reading the internal key-value files in /run | 10:34:23 |
| 9 Mar 2023 |
@lily:lily.flowers | Janne Heß: Do you think you could clarify the license situation for https://github.com/helsinki-systems/plymouth-theme-nixos-bgrt? I would like to package it in nixpkgs, if that's okay | 23:45:27 |
| 10 Mar 2023 |
@hexa:lossy.network | oh, a spinning logo 😄 | 00:05:24 |
@hexa:lossy.network | i want it | 00:05:34 |
@hexa:lossy.network | Janne Heß: make it happen! | 00:05:40 |
@janne.hess:helsinki-systems.de | In reply to @lily:lily.flowers Janne Heß: Do you think you could clarify the license situation for https://github.com/helsinki-systems/plymouth-theme-nixos-bgrt? I would like to package it in nixpkgs, if that's okay Sure, what do you want? Mit? | 07:11:04 |
@janne.hess:helsinki-systems.de | Also have you tested it first? I don't even remember if it looks good | 07:13:13 |
@janne.hess:helsinki-systems.de | In reply to @janne.hess:helsinki-systems.de Sure, what do you want? Mit? Or does it have to be CC-BY? that's what the logo is under. If only licensing wasn't what it is… | 07:33:46 |
@lily:lily.flowers | In reply to @janne.hess:helsinki-systems.de Or does it have to be CC-BY? that's what the logo is under. If only licensing wasn't what it is… I mean the logo is cc-by and not cc-by-sa, so it doesn't necessarily need to be the same license. It just needs to have attribution | 08:12:58 |
@lily:lily.flowers | In reply to @janne.hess:helsinki-systems.de Also have you tested it first? I don't even remember if it looks good Yeah it does look good! | 08:13:11 |
@lily:lily.flowers | I would say easiest is to just keep cc-by, though, same as the logo (my not-a-lawyer understanding is that cc licenses better accomodate creative works like this anyway rather than something like MIT) | 08:16:08 |
@janne.hess:helsinki-systems.de | https://library.mit.edu.au/copyright/creativecommons
Looks like a readme attribution is enough. I wanted mit because it would be compatible with nixpkgs | 08:28:42 |
@lily:lily.flowers | Yeah, just readme attribution is sufficient. It should be compatible with nixpkgs either way (pretty sure there's already cc assets in the repo), I mostly just care that it's licensed at all | 08:45:09 |