pywal16: init at 3.5.3

[MyGitHubBlueberry]

Description of changes

This is fork of pywal, named pywal16, maintained by eylles.
This package generates color palletes based on wallpaper, but it does it in 16 and not 8 color palette.
Some packages support pywal16 already, as original pywal replacement wpgtk will be a good example.

Motivation:

• This package is quite nice, I would use it myself
• Fixes pywal 8 color problem
• eylles, the package developer, is building handy git repo whith a templates for gui apps, and as person who uses wallust (pywal alternative), I would love to switch to something with gtk-qt support.

Note:

• I build package on my nixos with nix flakes and it works all right. Idk if it is "applicable" testing, so I won't tick this box.
• I have read contributing.md, but I'm not sure if I did everything ok, so this box is also unticked.

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/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 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.

---

Add a 👍 reaction to pull requests you find important.

[Qyriad]

Thank you for this, @MyGitHubBlueberry — could you change the commit message and PR title to match the convention for new packages? ofborg is very picky and only understands commits of a specific format.

[Qyriad]

This also has to be added to pkgs/top-level/python-packages.nix or it won't actually be accessible in Nixpkgs. i.e., checking out this PR as is, nix-build -A python3Packages.pywal16 does not work.

[MyGitHubBlueberry]

Thank you for this, @MyGitHubBlueberry — could you change the commit message and PR title to match the convention for new packages? ofborg is very picky and only understands commits of a specific format.

On it.

[MyGitHubBlueberry]

@Qyriad, thank you, all done.

[Qyriad]

This still needs an entry in pkgs/top-level/python-packages.nix or it won't actually be accessible in Nixpkgs. If I check out this PR right now, I can't actually build the package with something like nix-build -A python3Packages.pywal16 or nix build '.#python3Packages.pywal16'

[MyGitHubBlueberry]

@Qyriad sorry, I'm not very comfortable with git and github and I only now noticed that you actually suggested changes and not only description how to make them.
Again, thank you :)

[MyGitHubBlueberry]

@Qyriad is there anything else I need to do?

[Qyriad]

Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

• python311Packages.pywal16
• python311Packages.pywal16.dist
• python312Packages.pywal16
• python312Packages.pywal16.dist

Result of nixpkgs-review run on aarch64-darwin 1

4 packages built:

• python311Packages.pywal16
• python311Packages.pywal16.dist
• python312Packages.pywal16
• python312Packages.pywal16.dist

[Qyriad]

LGTM, sorry for the wait

[MyGitHubBlueberry]

@Qyriad there is no rash, thank you for your time.
You sent reviews, so can I tick the box aarch64-darwin?
And still, do I need to do anything, or should I just wait for the package to be merged?

[Qyriad]

Those checkboxes (I think) are for things you did. There is now at least one approval though, so hopefully a committer will be able to look at this PR soon

[MyGitHubBlueberry]

Thank you for you review :)

[wegank]

I'm not sure what's going on here, but the package was added in #316805 in a different way, so this PR can't be merged. Please add the patches in another PR if they are necessary.