| 1 Aug 2021 |
 David Arnold (blaggacao) | Docs are already updated: https://devos.divnix.com/bud/index.html đ | 21:41:51 |
| David Arnold (blaggacao) | kraftnix: https://github.com/divnix/bud/commit/612228a68d404d559405225427a5d8b3cef9d27c | 22:08:21 |
| David Arnold (blaggacao) | * kraftnix: https://github.com/divnix/bud/commit/612228a68d404d559405225427a5d8b3cef9d27c (impacience won) đ | 22:08:32 |
| David Arnold (blaggacao) | And here is the yeet branch: https://github.com/divnix/bud/tree/yeet | 22:10:52 |
 @kraftnix:matrix.org | In reply to @blaggacao:matrix.org
I'm not sure if sharing profiles would be really a good idea, in theory. Modules are the "generics" and profiles the concrete implementation. I find it to be a good balance between convenience and responsibility to pass "ownership" of any concrete implementation to the user. btw, regarding this discussion above, I would vote for being able to share profiles. while i agree that profiles tend to be a concrete implementation of something, it is still very useful for sharing. I often build profiles in a layered / more abstract fashion where nearly everything except host specific configuration is set in profiles.
i think profile sharing definitely aligns with devos' goals to allow quick bootstrapping and sharing of configurations. e.g. I could take nrdxp steam-compositor profile and mkForce whatever I want after that if I don't like it (or alternatively rewrite it all if theres too much), I could even have my own profiles which rely on "upstream" profiles.
it also aligns with goals such as, "use this profile, it's a perfect neovim/zsh/nix/python environment that builds in a language server with nice mappings etc.", a proper fully featured portable shell, i don't know who you would easily share that without the ability to export profiles
| 22:15:49 |
| @kraftnix:matrix.org | In reply to @blaggacao:matrix.org
I'm not sure if sharing profiles would be really a good idea, in theory. Modules are the "generics" and profiles the concrete implementation. I find it to be a good balance between convenience and responsibility to pass "ownership" of any concrete implementation to the user. * btw, regarding this discussion above, I would vote for being able to share profiles. while i agree that profiles tend to be a concrete implementation of something, it is still very useful for sharing. I often build profiles in a layered / more abstract fashion where nearly everything except host specific configuration is set in profiles.
i think profile sharing definitely aligns with devos' goals to allow quick bootstrapping and sharing of configurations. e.g. I could take nrdxp steam-compositor profile and mkForce whatever I want after that if I don't like it (or alternatively rewrite it all if theres too much), I could even have my own profiles which rely on "upstream" profiles.
it also aligns with goals such as, "use this profile, it's a perfect neovim/zsh/nix/python environment that builds in a language server with nice mappings etc.", a proper fully featured portable shell, i don't know how you would easily share that without the ability to export profiles
| 22:16:48 |
 @timdeh:matrix.org | I only advocate for this because it was my original goal for DevOS, though the community branch unfortunately never took off âšī¸ | 22:17:18 |
| @kraftnix:matrix.org | i think the community branch is too centralised of a solution, we should be leveraging flakes :) | 22:17:44 |
| David Arnold (blaggacao) | I think walking the config tree and replace values by mkDefault would be actually a good thing, i possible, before exporting profiles. | 22:17:59 |
| David Arnold (blaggacao) | Can wee peek if that's possible? | 22:18:25 |
| @timdeh:matrix.org | In reply to @kraftnix:matrix.org
i think the community branch is too centralised of a solution, we should be leveraging flakes :) exactly my thinking | 22:22:16 |
| @timdeh:matrix.org | I mean couldn't we just mapAttrs over a profile? | 22:30:45 |
| @timdeh:matrix.org | nvm, I guess that wouldn't work in the case of a lambda | 22:38:37 |
| 2 Aug 2021 |
| David Arnold (blaggacao) | We could also just export them and see how it goes and what the problems are đ | 13:23:29 |
|  yuu joined the room. | 14:11:03 |
| @timdeh:matrix.org | oh, I was also wondering if this could be useful to us:
https://github.com/jonringer/nix-template | 16:06:37 |
| David Arnold (blaggacao) | I guess we'd have to onboard Jon onto devos, first đ | 17:25:55 |
| @timdeh:matrix.org | last I checked with him, he was still using legacy nix for his system (unless I remember wrong) | 17:41:23 |
| David Arnold (blaggacao) | We need more đĨđĨđĨđĨ | 17:41:56 |
| @timdeh:matrix.org | always đ | 17:45:12 |
| @timdeh:matrix.org | has anyone else stumbled upon this subdir of nix proper:
https://github.com/NixOS/nix/tree/master/nix-rust | 17:45:27 |
 yusdacra | In reply to @timdeh:matrix.org
has anyone else stumbled upon this subdir of nix proper:
https://github.com/NixOS/nix/tree/master/nix-rust Yeah, is it used somewhere? | 17:46:03 |
| David Arnold (blaggacao) | In reply to @timdeh:matrix.org
has anyone else stumbled upon this subdir of nix proper:
https://github.com/NixOS/nix/tree/master/nix-rust I hope it revives / resurrects. | 17:46:11 |
| @timdeh:matrix.org | In reply to @yusdacra:nixos.dev
Yeah, is it used somewhere? That's what i want to know đ | 17:46:44 |
| @timdeh:matrix.org | We need to allocate funds to this immediately đ | 17:48:07 |
| @timdeh:matrix.org | (as if I have any control over that đ) | 17:48:18 |
| yusdacra | Unofficial Nix Rust Roadmap đ | 17:48:45 |
| David Arnold (blaggacao) | In reply to @timdeh:matrix.org
We need to allocate funds to this immediately đ The european union has money for those kind of things. We just need a european company to sponsor the application for grants | 17:51:03 |
| David Arnold (blaggacao) | If I look at how some rust projects thrive, it seems that there are fresh and extremely motivated people in that ecosystem. | 17:52:07 |
| David Arnold (blaggacao) | Ultimately, it's people! Neither money, nor tech. | 17:52:33 |
