marcel: init at 0.22.2

[KUD-00]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

It's my first time to contribute. I apologize first for any mistakes in the codes. I have tested the binary in /result/bin(in nix-shell - A marcel environment), but not sure if it is executable when installing it on any system. I tried $ nix-env -f . -iA marcel but it said it can't find lib and many other parameters. I'm not sure is it good to use /run/current-system/sw/bin/bash

[eclairevoyant]

Fixes #263995

[TomaSajt]

I requested some changes about using the latest version

[TomaSajt]

LGTM
Please, could you restructure your commits, so that there are only 2 commits: one called maintainers: add kud, which only has the maintainer-list.nix change, and another one called marcel: init at 0.20.0, which has every other change.
If you need help with this, I can help.

[KUD-00]

@TomaSajt now it seems only contains 2 commits. Thank you for your instructions!

[MaxwellDupre]

format = "setuptools";
is now
pyproject = true;

And usually the these changes are split (ie 2 PRs):

1. for maintainers-list
2. marcel

[eclairevoyant]

And usually the these changes are split (ie 2 PRs):

1. for maintainers-list

2. marcel

No, they are usually one PR, adding to maintainers list isn't usually approved unless you have some package to maintain.

[AndersonTorres]

And usually the these changes are split (ie 2 PRs):

No need for a new Pull Request. A commit suffices

adding to maintainers list isn't usually approved unless you have some package to maintain.

This is at the discretion of the committers.

E. G. Sometimes the person wants to contribute to multiple packages at once, then it is better to do a PR for maintainers list update first.

[KUD-00]

now using pyproject = true

I'm not sure why it seems I need to add setuptools into propagatedBuildInputs, according to this comment, pyproject = true should equals to format = setuptools.

[eclairevoyant]

Thanks for the contribution and patience - one more point of feedback from my side before I'd consider it mergeable. Also FYI 0.22.2 is out

[ghost]

looks good -- minor issue with setuptools, it should not get propagated as it is just used to build the package and the substituteInPlace is not needed as python3 is already in the path.

validated maintainer info matches:

curl -s https://api.github.com/users/KUD-00|jq '{name,github:.login,githubId:.id}'