New port: games/voxelands, a voxel sandbox game forked from minetest
Details
Details
- Reviewers
swills AMDmi3 - Commits
- rP425080: New ports: games/voxelands and games/voxelands-server
portlint -AC: OK
testport: OK (poudriere: 9.3-RELEASE-p48, i386, default options)
testport: OK (poudriere: 9.3-RELEASE-p48, amd64, default options)
testport: OK (poudriere: 10.3-RELEASE-p10, i386, default options)
testport: OK (poudriere: 10.3-RELEASE-p10, amd64, default options)
testport: OK (poudriere: 11.0-RELEASE-p1, i386, default options)
testport: OK (poudriere: 11.0-RELEASE-p1, amd64, default options)
Diff Detail
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 5735 Build 6034: arc lint + arc unit
Event Timeline
| games/voxelands/Makefile | ||
|---|---|---|
| 23–24 | Whenever I see CLIENT and SERVER as option, I wonder if there should not be two ports, one for the client, and one for the server. | |
Comment Actions
Mmmm, ok, I think the client should be called voxelands, as it is the name of the binary.
Also, I think the server should be slave'd to the client one as they come from the same tarball.
Your original Makefile was great, all you needed to do was add to it:
OPTIONS_SLAVE?= CLIENT OPTIONS_EXCLUDE?= SERVER
And create a voxelands-server port with only a Makefile with:
PKGNAMESUFFIX=-server
OPTIONS_SLAVE=SERVER
OPTIONS_EXCLUDE=CLIENT
MASTERDIR=${.CURDIR}../voxelands
.include ${MASTERDIR}/Makefile