| 10 Jul 2023 |
 @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 |
