Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qpakman: init at unstable-2024-03-07 #301876

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

not-leader
Copy link
Contributor

@not-leader not-leader commented Apr 5, 2024

Description of changes

Forum post describing older version of package: https://openarena.ws/board/index.php?topic=1710.0
Adds me (not_leader) as maintainer for package

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:
  • 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.

@not-leader not-leader changed the title qpakman: init at 2024-03-07 qpakman: init at unstable-2024-03-07 Apr 5, 2024
Copy link
Contributor

@jchv jchv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, just a few relatively minor comments. I just threw a quake1 shareware pak at it to test, basic functionality seems to be working fine:

$ nix run .#qpakman -- -l ~/Downloads/pak0.pak

**** QPAKMAN v0.67  (C) 2008 Andrew Apted ****

Opened PAK file: /home/john/Downloads/pak0.pak
--------------------------------------------------
   1: +0000000c 00001aa6 : sound/items/r_item1.wav
   2: +00001ab2 00001d18 : sound/items/r_item2.wav
   3: +000037ca 00001f16 : sound/items/health1.wav
   4: +000056e0 00002724 : sound/misc/medkey.wav
   5: +00007e04 000038f2 : sound/misc/runekey.wav
   6: +0000b6f6 00005808 : sound/items/protect.wav
   7: +00010efe 000084dc : sound/items/protect2.wav
   8: +000193da 00005b44 : sound/items/protect3.wav
   9: +0001ef1e 00003dee : sound/items/suit.wav
...

pkgs/by-name/qp/qpakman/package.nix Outdated Show resolved Hide resolved
description = "A command-line tool for managing PAK and WAD files from QuakeI/II & Hexen II";
longDescription = '''';
license = licenses.gpl2Plus;
maintainers = [ ];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to add yourself as a maintainer? To do so, you'll want to add yourself to maintainer-list.nix. See the documentation. I believe it is fine to do this in the same PR as other changes as long as it's in a separate commit before the commit adding the actual package.

pkgs/by-name/qp/qpakman/package.nix Outdated Show resolved Hide resolved
license = licenses.gpl2Plus;
maintainers = [ ];
platforms = platforms.unix;
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also set the mainProgram attribute of meta to qpakman? This will make things like nix run nixpkgs#qpakman work. Right now it will work since the pname and the mainProgram are the same, but this behavior is being deprecated, so derivations that have a "primary" program should set mainProgram from now on.

@ofborg ofborg bot added the 11.by: package-maintainer This PR was created by the maintainer of the package it changes label Apr 6, 2024
@not-leader not-leader closed this Apr 21, 2024
@not-leader not-leader reopened this Jul 24, 2024
@lavenderdotpet
Copy link

yipeeee

@lavenderdotpet
Copy link

@jchv any update on this?

pkgs/by-name/qp/qpakman/package.nix Outdated Show resolved Hide resolved
pkgs/by-name/qp/qpakman/package.nix Outdated Show resolved Hide resolved
pkgs/by-name/qp/qpakman/package.nix Outdated Show resolved Hide resolved
not-leader and others added 3 commits August 14, 2024 20:29
@lavenderdotpet
Copy link

sorry to ping again
any update on this?

@jchv
Copy link
Contributor

jchv commented Oct 14, 2024

FWIW I don't have commit access so I can't merge. There are some Discourse topics that are often used to try to get attention to a PR that has fallen by the wayside, though.

@jchv
Copy link
Contributor

jchv commented Oct 14, 2024

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 301876


x86_64-linux

✅ 1 package built:
  • qpakman

Copy link
Contributor

@jchv jchv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This still LGTM overall, but the commits need to be squashed, and the squashed commit message should follow the CONTRIBUTING.md specification. There can be multiple commits in a single PR, but there shouldn't be redundant commits (e.g. adding something then changing it immediately after, or adding something and reverting it.) I hate to be picky, but it's just part of the conventions.

homepage = "https://github.com/fhomolka/qpakman";
description = "command-line tool for managing PAK and WAD files from QuakeI/II & Hexen II";
license = licenses.gpl2Plus;
maintainers = [ ];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New packages must have a maintainer.

@FliegendeWurst FliegendeWurst added the awaiting_changes (old Marvin label, do not use) label Nov 6, 2024
@lavenderdotpet
Copy link

This still LGTM overall, but the commits need to be squashed, and the squashed commit message should follow the CONTRIBUTING.md specification. There can be multiple commits in a single PR, but there shouldn't be redundant commits (e.g. adding something then changing it immediately after, or adding something and reverting it.) I hate to be picky, but it's just part of the conventions.

the original poster @not-leader
told me that she is no longer using NixOS
and said "is there any way for someone else to do this?"

@FliegendeWurst
Copy link
Member

"is there any way for someone else to do this?"

Sure. Someone else can create a new PR based on this one.

@FliegendeWurst FliegendeWurst added 9.needs: maintainer Package or module needs active maintainers and removed awaiting_changes (old Marvin label, do not use) labels Nov 10, 2024
@lavenderdotpet
Copy link

"is there any way for someone else to do this?"

Sure. Someone else can create a new PR based on this one.

oof :c I need this tool for the dev work I do just sad to see it get delayed

@jchv
Copy link
Contributor

jchv commented Nov 10, 2024

Sorry to hear that this has been impacting you. It would be relatively easy for someone to adopt this, but I personally don't think I should as I am not a developer of Quake/Quake II mods and don't know a whole lot about qpakman.

If you would like to have this derivation as a part of your NixOS or nix-darwin configuration, it would not be too difficult to lift the derivation out of here and put it into your configuration for the time being. Just copy out the package.nix file, and then you should be able to callPackage on it, e.g.

{ pkgs, ... }:
{
  environment.systemPackages = [
    (pkgs.callPackage ./package.nix { })
  ];
}

It's also relatively easy to construct a Nix flake for qpakman that can be used with nix profile install or what have you.

Hopefully someone with subject matter experience will step up to be a maintainer so that it can be merged into Nixpkgs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.has: package (new) This PR adds a new package 9.needs: maintainer Package or module needs active maintainers 10.rebuild-darwin: 1-10 10.rebuild-darwin: 1 10.rebuild-linux: 1-10 10.rebuild-linux: 1 11.by: package-maintainer This PR was created by the maintainer of the package it changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants