plink2: init at 2.0.0-a.7.6

[GaetanLepage]

Things done

Add PLINK 2.0 (alpha), a free, open-source whole genome association analysis toolset, designed to perform a range of basic, large-scale analyses in a computationally efficient manner.

cc @RaulPPelaez

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.
• Follows the automation/AI policy.

[GaetanLepage]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 563938
Commit: 68982e78976732a22df02d302aa18447acd8335b

---

x86_64-linux

✅ 1 package built:

• plink2

---

aarch64-linux

✅ 1 package built:

• plink2

---

aarch64-darwin

✅ 1 package built:

• plink2

[pbsds]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 563938
Commit: 68982e78976732a22df02d302aa18447acd8335b

---

x86_64-linux

✅ 1 package built:

• plink2

---

aarch64-linux

✅ 1 package built:

• plink2

---

aarch64-darwin

✅ 1 package built:

• plink2

[pbsds]

• package path fits guidelines
• package name fits guidelines
  • matches debian, to verify this i used https://pkgs.org/search/?q=plink2 since repology is down
• package version fits guidelines
• package builds on x86_64-linux
• executables tested on x86_64-linux
• meta.description is set and fits guidelines
• meta.license fits upstream license
• meta.platforms is set
• meta.maintainers is set
• meta.mainProgram is set, if applicable.
• build time only dependencies are declared in nativeBuildInputs
• source is fetched from an official or trusted location
  • matches debian
• source is fetched using the appropriate function
• the motives for any special packaging choices are documented
• the list of phases is not overridden
• when a phase (like installPhase) is overridden it starts with runHook preInstall and ends with runHook postInstall.
• patches have a comment describing either the upstream URL or a reason why the patch wasn't upstreamed
• patches that are remotely available are fetched rather than vendored