| 6 Feb 2023 |
 infinisil | There was also a discussion yesterday about parallelising the work more | 15:26:34 |
| infinisil | I think it all hinges on making that first RFC a success though | 15:27:56 |
 growpotkin ( Alex Ameen ) | A fool proof way to depend on a particular version is a pinned form of Nixpkgs in a flake. You can pin an arbitrary number and create an overlay to cherry pick. | 15:30:15 |
| growpotkin ( Alex Ameen ) | Override is your friend also | 15:31:01 |
| infinisil | Ehh, overlays and overrides have serious composability problems, I really think we need something better to replace them | 15:31:22 |
| infinisil | John Ericson Robert Hensing (roberth) tomberek: Joining? | 15:32:26 |
 @blaggacao:matrix.org | Gytis Ivaskevicius: from a 30s look the blueprints idea is almost 100% overlap with RFC140. Correct me if I'm wrong. | 16:19:12 |
| @blaggacao:matrix.org | 
Download pkg-evolution.png | 16:21:03 |
| @blaggacao:matrix.org | It would be pkg-fun, I guess. | 16:21:16 |
 Gytis Ivaskevicius | In reply to @growpotkin1:matrix.org
A fool proof way to depend on a particular version is a pinned form of Nixpkgs in a flake. You can pin an arbitrary number and create an overlay to cherry pick. My option gives you a possibility of doing that | 16:24:41 |
| @blaggacao:matrix.org | Beyond features, though, the name of the game is the process to obtain convergence and wide-spread adoption. | 16:27:23 |
| @blaggacao:matrix.org | * Beyond features, though, the name of the game is the process to obtain convergence and wide-spread adoption. | 16:27:40 |
| @blaggacao:matrix.org | In reply to @infinisil:matrix.org
I think it all hinges on making that first RFC a success though Or ^^ this, in other words. | 16:29:11 |
 tomberek | In reply to @gytis-ivaskevicius:matrix.org
Hey guys, not sure what you guys are up to these days but I'd appreciate if you guys could follow up on this blueprints idea, maybe making it a standard in nix ecosystem
https://github.com/NixOS/nixpkgs/pull/208020#issuecomment-1419168718 Yes.... the blueprints concept is something I'd like to examine and shepherd. | 18:00:05 |
 Winter (she/her) | In reply to @blaggacao:matrix.org
It just got harder and became an evangelization issue after playing a little with it. But that's borderline off topic, here, anyways. Can I ask what this issue is even saying? I'd consider myself very experienced in Nix and yet I am very, very confused. | 18:28:59 |
| Winter (she/her) | If I'm this confused, I'd say the upstream maintainers are absolutely clueless as to what you're saying -- I don't even see a call to action or anything. | 18:31:07 |
| infinisil | I think it's David Arnold (blaggacao) trying to make a point for adding a Nix build, maybe it should be linked to https://github.com/frappe/bench/pull/1429 | 18:31:10 |
| @blaggacao:matrix.org | There are so many different ways to approach Nix. It's always a gamble.
This istance asumes maintainers are familiar with PATH and sys.addsitedirs() and tries yo explain what it does for them in a two-script capsule what they currently have been trying to achieve with multiple ansible playbooks. | 18:45:33 |
| @blaggacao:matrix.org | * There are _so_ many different ways to approach Nix. It's always a gamble.
This istance assumes maintainers are familiar with `PATH` and `sys.addsitedirs()` and tries yo explain what it does for them in a two-script capsule what they currently have been trying to achieve with multiple ansible playbooks. | 18:45:48 |
| @blaggacao:matrix.org | * There are _so_ many different ways to approach Nix. It's always a gamble.
This istance assumes maintainers are familiar with `PATH` and `sys.addsitedirs()` and tries to explain what it does for them in a two-script capsule.
As soon as they refuse to get distracted by wired path names, they will recognize the packages and libraries that they currently are procuring via ansible playbooks in a very heavy handed approach that makes up 20% of the `bench` codebase. | 18:47:24 |
 @piegames:matrix.org |
There are so many different ways to approach Nix. It's always a gamble.
If your way of approaching Nix results multiple people already deeply familiar with Nix saying that they don't understand your text (add me to that list, I read the code blocks twice and they still look like some arcane spell to me), then I guarantee you'll lose that gamble for everybody else too.
| 21:49:01 |
| @piegames:matrix.org |
evangelization issue
As soon as they refuse to get distracted by wired path names, they will recognize the packages and libraries that they currently are procuring via ansible playbooks in a very heavy handed approach that makes up 20% of the bench codebase.
I can't really put it into words, but I find those sentences deeply unsettling. It gives me the vibes of some pretentious 16th century missionary trying to convert those primitive people or something. (I apologize for the metaphor, but it currently best describes how I feel about this.)
I know there are running jokes about Nix being a cult/sect/religion and about "converting" people to Nix, yet I've never felt it being hostile until now
| 21:49:04 |
| @blaggacao:matrix.org | Once language and stance becomes a distraction itself, it's a sign for me to go fish. Thank you. | 22:05:32 |
| @blaggacao:matrix.org | I feel also really uncomfortable that we discuss this here, off topic. Apologies to everybody! | 22:06:31 |
| @blaggacao:matrix.org left the room. | 22:06:43 |
| 7 Feb 2023 |
 John Ericson | https://discourse.nixos.org/t/adding-pkg-config-metadata-to-nixpkgs-packages/25281 | 04:21:58 |
 Sandro | In reply to @Ericson2314:matrix.org
https://discourse.nixos.org/t/adding-pkg-config-metadata-to-nixpkgs-packages/25281 The design of this seems really rushed to me. Immediately several people noted the boiler platy parts and why it doesn't happen automatically when meta.pkgConfigModules is provided. | 12:16:26 |
| Sandro | also on a side note: pkgConfigModules looks kinda strange in camel. | 12:16:45 |
| John Ericson | Sandro 🐧: to be clear that is not an official project of this Nixpkgs Arch team | 12:33:08 |
| Sandro | we can also move this discussion to #dev:nixos.org | 14:39:21 |
