| 7 Jul 2023 |
 figsoda | hmm the two darwin dependencies comes from the same go package | 22:23:32 |
| figsoda | github.com/getlantern/systray | 22:23:36 |
| figsoda | oh | 22:27:13 |
| figsoda | so it seems like this dependency is only for windows and darwin | 22:27:22 |
| figsoda | https://github.com/Unpackerr/unpackerr/blob/5e783174c381caa94132cf71b8669416481808c9/pkg/unpackerr/tray.go#L1 | 22:27:22 |
| figsoda | idk what I can do with that, I would have to parse go files | 22:27:34 |
 @kranzes:matrix.org | Cringe | 22:49:10 |
| @kranzes:matrix.org | Go once again proving that it has one of the worst packaging ecosystem out of any other modern language | 22:49:59 |
| 9 Jul 2023 |
|  @kokern:matrix.org changed their profile picture. | 22:28:39 |
| 10 Jul 2023 |
 @blaggacao:matrix.org | Is there a mapper for nixpkgs moves like this?
error: poetry was promoted to a top-level attribute, use poetry-core to build Python packages
| 01:21:56 |
| @blaggacao:matrix.org | Not sure if this should be a nix-init concern, though. | 01:22:07 |
| @blaggacao:matrix.org | That could potentially grow pretty wild. | 01:22:22 |
| figsoda | this would require patching the source code to use poetry-core instead of poetry | 01:23:51 |
| figsoda | it is technically possible with nix-init, but i think the patch should preferably be submitted to upstream | 01:25:23 |
| figsoda | maybe the best move is for nix-init to add poetry-core and print a warning stating that the source code needs to be patched | 01:25:55 |
| @blaggacao:matrix.org | I've two more that may be in scope:
- https://github.com/NixOS/nixpkgs/pull/242542#discussion_r1257646145
- https://github.com/NixOS/nixpkgs/pull/242542#discussion_r1257647353
| 02:39:32 |
| @blaggacao:matrix.org | TL;DR
(pythonOlder 3.9) if pyproject states itmeta.changelog if it's a github package (maybe)
| 02:40:28 |
| figsoda | added to https://github.com/nix-community/nix-init/issues/64 | 02:41:42 |
| figsoda | *
(pythonOlder 3.9) if pyproject states it
added to https://github.com/nix-community/nix-init/issues/64
| 02:41:54 |
| figsoda | I'm still a bit unsure about what to do with changelog in release notes, i've found myself manually adding those, but i couldn't find a good way to programmatically identify whether the release has meaningful release notes | 02:42:48 |
| figsoda | meaningful ~= anything more than the last commit message | 02:44:01 |
| @blaggacao:matrix.org | Yeah, agree. Impossible to give a good judgment with heuristics.
Are code comments in scope for nix-init?
| 02:47:40 |
| figsoda | I haven't explored with comments, but yes I would say so | 02:48:17 |
| @blaggacao:matrix.org | like so:
# TODO: uncomment if helpful
# changelog = "https://github.com/annotated-types/annotated-types/releases/tag/${src.rev}";;
| 02:48:28 |
| figsoda | anything that would help with packaging a program really | 02:48:40 |
| @blaggacao:matrix.org | I'm going right now crazy with nix-init... packaging essentially 7 python packages in parallel | 02:49:23 |
| figsoda | In reply to @blaggacao:matrix.org
like so:
# TODO: uncomment if helpful
# changelog = "https://github.com/annotated-types/annotated-types/releases/tag/${src.rev}";;
I will consider that, thanks | 02:49:41 |
| figsoda | i would still prefer heuristics if it works | 02:49:59 |
| figsoda | but maybe something like this could also work | 02:50:09 |
| @blaggacao:matrix.org | A small oped (ode) to nix-init | 11:41:46 |
