| 20 Apr 2025 |
|  rocky (she/they) 🏳️⚧️ joined the room. | 17:41:37 |
| rocky (she/they) 🏳️⚧️ | Hello :3 | 17:42:29 |
| rocky (she/they) 🏳️⚧️ | I was wondering if Nix is suitable for monorepo development | 17:44:06 |
| rocky (she/they) 🏳️⚧️ | Is it kind of like Bazel, good for multilingual monorepo projects? | 17:46:07 |
 djacu | Nixpkgs is the largest public package repository on the Internet. So I'd say yes | 18:24:57 |
 Morgan (@numinit) | I'd say so. Also, all the dependencies are self contained in nixpkgs, unlike Bazel. | 18:39:45 |
|  mannp changed their profile picture. | 22:01:46 |
| 21 Apr 2025 |
|  @golanv:envs.net joined the room. | 03:45:11 |
|  palekiwi joined the room. | 03:47:34 |
|  @shortdom:matrix.org removed their display name shortdom. | 07:26:57 |
| @shortdom:matrix.org left the room. | 07:27:22 |
|  softwing 🩷💛🤍💜💙 (he/they/it) changed their display name from softwing 🩷💛🤍💜💙 (he/they/it/she) to softwing 🩷💛🤍💜💙 (he/they/it). | 14:19:37 |
|  @scm:sven.cc left the room. | 15:32:13 |
|  @jh-devv:matrix.org left the room. | 16:48:14 |
|  wesleyjrz changed their profile picture. | 17:48:32 |
| 22 Apr 2025 |
|  danish joined the room. | 01:25:23 |
|  Evest joined the room. | 10:19:03 |
| Evest set a profile picture. | 10:22:30 |
|  Thomas joined the room. | 17:11:20 |
 Pol | I don't know if this is the right channel to ask that, but here we go. I made this little proof of concept library at work: https://code.europa.eu/pol/ec-lib/
The problem is that when it is used in another flake, running nix flake show prints the logo multiple times.
The logo is just a fancy builtins.trace call to a text file with the logo of the company.
I'm trying to find solution to avoid printing it only when the functions exposed in the flake overlay are used, without luck. Do you have a suggestion for me? | 18:21:22 |
|  @adarcy:matrix.org left the room. | 19:04:11 |
 Matt Sturgeon | My understanding of how builtins.trace works is that it will print every time the wrapped expression gets evaluated. Sometimes moving your trace to a "more global" let-binding can cause the value to be reused more reliably, leading to fewer prints.
Without looking, another possibility here is that your logo-printer is being used in multiple flake outputs (or maybe in a per-system output), so it is getting run when each of those outputs are evaluated by nix flake show?
Finally; if you have a flake that is calling your logo-printer and one of your input flakes are also calling a logo-printer on an output used by your flake, that would lead to seeing multiple logos.
| 22:17:36 |
| 23 Apr 2025 |
|  @slamphear:matrix.org joined the room. | 05:23:25 |
 piegames | You could move the trace code into a file you import to take advantage of import caching | 06:23:33 |
| piegames | However, in the end you will always be relying on implementation details, as trace was not built for such purposes | 06:24:08 |
| Pol | Thanks for your inputs. Indeed, builtins.trace was not made for this purpose and I shouldn't try to bend stuff as I do. | 08:47:50 |
|  twix ⚡️ joined the room. | 11:58:53 |
|  jul1u5 changed their profile picture. | 18:31:42 |
|  GalaxyNova joined the room. | 19:19:48 |
|  Anton joined the room. | 21:56:49 |
