[Bug 251608] Revive games/endgame-singularity and take maintainership

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251608

            Bug ID: 251608
           Summary: Revive games/endgame-singularity and take
                    maintainership
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: cyberbotx at cyberbotx.com

Created attachment 220282
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220282&action=edit
endgame-singularity-1.00.patch

games/endgame-singularity was removed due to it using Python 2.7. The game was
updated to use Python 3.x about a month before it was removed from the ports
tree, but the port was not updated in time. This patch updates it to the latest
version that uses Python 3.x. diff was run against the last SVN revision that
the port was in the ports tree (544926).

Because the previous maintainer did not update the port before its removal, I
would like to take maintainership with this revival.

* Update Makefile
* Update distinfo
* Update pkg-plist
* Add files/patch-singularity_code_dirs.py

The patch allows the game to read from the port's data directory under
${PREFIX}/share, as the unmodified game puts that data under its python
site-packages directory instead. These changes also allows the existing
games/endgame-singularity-music port to be left unchanged, as well as putting
the data in a place more applicable to FreeBSD's directory structure.

Changelogs:

https://github.com/singularity/singularity/releases/tag/singularity-1.0a1
https://github.com/singularity/singularity/releases/tag/v1.0a2
https://github.com/singularity/singularity/releases/tag/v1.0b1
https://github.com/singularity/singularity/releases/tag/v1.00

Passes portlint. Tested in poudriere for 11 and 12.

-- 
You are receiving this mail because:
You are the assignee for the bug.