| 23 Apr 2023 |
|  denna left the room. | 12:45:17 |
| 25 Apr 2023 |
|  trofi left the room. | 21:31:45 |
| 26 Apr 2023 |
 tea | I think this is maybe in the scope for this team?
Where should I store things that are
- generated
- not needed at eval time
- but nixpkgs-tooling specific
- too large (like 2mb) to include in nixpkgs
| 15:40:10 |
 Wanja Hentze | I don't have an answer but maybe look at https://github.com/NixOS/rfcs/pull/109 | 15:44:40 |
 Alyssa Ross | noob_tea: can you explain again to me what this file is? | 16:30:31 |
| tea | In reply to @qyliss:fairydust.space
noob_tea: can you explain again to me what this file is? things like https://privatebin.net/?94cb53df2da29957#GhwCJiSyex4V4CPgw3fEJFwSEB5rBE1UfdZ8vgnujHW5 | 17:00:44 |
| tea | or cc | 17:00:47 |
| Alyssa Ross | why are we redistributing a binary form in Nixpkgs? | 17:01:19 |
| tea | In reply to @qyliss:fairydust.space
why are we redistributing a binary form in Nixpkgs? i have update tooling for flutter and dart specific things.
it is a rust program.
it uses dependencies.
don't you think that will apply there | 17:05:16 |
| Alyssa Ross | Hydra redistributes binary forms | 17:05:59 |
| Alyssa Ross | Nixpkgs does not | 17:06:07 |
| tea | yes. | 17:06:09 |
| tea | In reply to @qyliss:fairydust.space
Nixpkgs does not but I am making it redistribute a binary form | 17:06:24 |
 K900 | I think the pastebin link is wrong | 17:06:27 |
| Alyssa Ross | As you'll have noticed, Hydra does not in general comply with terms like that. | 17:06:38 |
| Alyssa Ross | It should, but currently it does not. | 17:06:48 |
| Alyssa Ross | This is a problem that we need to fix in general, but it's not a problem that we need to fix for one single tool. | 17:07:13 |
 figsoda |
generated
not needed at eval time
doesn't that mean you can just build from source in nixpkgs?
| 17:09:00 |
| figsoda | if it can't be built from source, it is probably best to be hosted in a separate repo and fetched in nixpkgs | 17:09:56 |
| figsoda | * if it can't be built from source, it is probably best to have it hosted in a separate repo and fetched in nixpkgs | 17:10:07 |
| 27 Apr 2023 |
|  @eisfunke:eisfunke.com joined the room. | 15:23:25 |
| 2 May 2023 |
|  dish [Fox/It/She] joined the room. | 03:48:41 |
| dish [Fox/It/She] changed their display name from Pyrox to Pyrox [ She/They/Xem ]. | 13:29:08 |
 infinisil | @room: The next meeting will take place in ~15 minutes - meeting link - live stream - meeting notes | 14:17:53 |
| infinisil | Robert Hensing (roberth): growpotkin ( Alex Ameen ): John Ericson: Meeting time | 14:32:06 |
 SomeoneSerge (matrix works sometimes) | RE: use-cases/ in nixpkgs-architecture/pkgs-modules
How would you format these? Did you have executable examples in mind, or just the prose in .md files?
| 15:03:09 |
| infinisil | Someone S: #wg-pkgs-modules:matrix.org is probably better :) | 15:16:57 |
| infinisil | Growpotkin: Since you mentioned it, can you briefly check whether there are any collisions in nixpkgs? | 15:26:35 |
 growpotkin1 | Yeah | 15:26:56 |
| infinisil | growpotkin ( Alex Ameen ): And then report the result with a review comment in the RFC, suggesting an edit, that would be great :) | 15:27:10 |
