cwm: 5.6 -> 6.3, and myself as maintainer

[mkf]

Motivation for this change

There were huge changes in the syntax and feature set of the cwmrc language, cwm users coming from distros of it such as archlinux or openbsd that have it up-to-date faced the necessity to either abandon cwm and their cwmrc, or to install newer cwm privately if savvy enough, or to rework their whole cwmrc and get used to lack of features and outdated way of operation, from before changes made over a time of something like five years.

Things done

cwm: 5.6 -> 6.3-80-g4154b9b, and i added myself as the sole maintainer, adding myself to maintainers-list for that.

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[mkf]

after i mentioned it on fediverse and while i wasnt looking there, @0x4A6F made his own patch, somewhat better in fixing a few things although not onto linux branch (80 commits forward from v6.3 tag) of the Leah's cwm repo but onto but the v6.3 tag of Leah's cwm repo

https://github.com/0x4A6F/nixpkgs/tree/master-cwm

although idk whether i should PR merging v6.3 or v6.3-80, and also whether i should even do more force-pushes

ahhh this rebasing and unability to test what i merge is so bothersome, i am considering switching to nixpkgs:master on my daily driver machine now but idk if i should

[0x4A6F]

Welcome @mkf, I hope RFC-0053: defining pull-request workflow will make this process clearer.

I've picked the latest version from repology/projects/cwm.

You could import this PR to your configuration.nix and test from there.

environment.systemPackages = with pkgs; [
  (import (builtins.fetchTarball https://github.com/NixOS/nixpkgs/archive/pull/70018/head.tar.gz) {}).cwm
];

[mkf]

@0x4A6F you said "latest version from repology", while taking a glance of two top AUR entries there, cwm and cwm-git, looking at their PKGBUILDs, first takes v6.3 tag and the cwm-git takes linux branch , that is v6.3-80-g4154b9b as of now, so that leaves the consideration still up

afaik that project is about porting a version of cwm deemed stable for openbsd, so retaining the version numbering from there, and then making subsequent fixes, porting that version to linux. so i suppose that maybe what is in that linux branch is actually already deemed stable and not just a development branch

although yeah maybe it would be better to first merge the older tagged revision, then investigate how stable can linux branch be considered, and maybe then consider putting up a newer ref in another MR.

---

also, when i use that snippet i won't be testing against master but against my 19.03, while proposing a merge into master so not really testing the merge that i propose a commit of

(thanks for that snippet tho)

[0x4A6F]

According to nixpkgs/manual/#sec-package-naming and nixpkgs/manual/#sec-versioning cwm/default.nix should be for a release.
Versions from commits should be named cwm-unstable-YYYY-MM-DD.

[jonringer]

@GrahamcOfBorg build cwm