From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-fps/freedoom-data/
Date: Tue, 18 Jun 2019 21:23:22 +0000 (UTC) [thread overview]
Message-ID: <1560892831.6d3f99b17a5f609a1ebc4330ab9cb7d9aef849b5.chewi@gentoo> (raw)
commit: 6d3f99b17a5f609a1ebc4330ab9cb7d9aef849b5
Author: William Breathitt Gray <vilhelm.gray <AT> gmail <DOT> com>
AuthorDate: Fri Jun 14 09:29:43 2019 +0000
Commit: James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Tue Jun 18 21:20:31 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6d3f99b1
games-fps/freedoom-data: New package
Package-Manager: Portage-2.3.67, Repoman-2.3.14
Signed-off-by: William Breathitt Gray <vilhelm.gray <AT> gmail.com>
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>
games-fps/freedoom-data/Manifest | 1 +
.../freedoom-data/freedoom-data-0.11.3.ebuild | 29 +++++++++++++++
games-fps/freedoom-data/metadata.xml | 42 ++++++++++++++++++++++
3 files changed, 72 insertions(+)
diff --git a/games-fps/freedoom-data/Manifest b/games-fps/freedoom-data/Manifest
new file mode 100644
index 00000000000..d3ca3066e92
--- /dev/null
+++ b/games-fps/freedoom-data/Manifest
@@ -0,0 +1 @@
+DIST freedoom-0.11.3.zip 18889307 BLAKE2B 052d7f58d1beb7947f4fff3021ec0229c9746bfb7970a52d23fa44fc881d8cf3c314b8ecf0dc400c2da4e28c623695874ae75dcd1e45933fdb1826ea04f0e24b SHA512 c67fc69bca87cba2ba40b91f578724feaabbd6cd64c6845fa567d6901b7a9e3145185011731c677a71f7b5a6f8707855fb573c0c09b6d47fef83b1577b211816
diff --git a/games-fps/freedoom-data/freedoom-data-0.11.3.ebuild b/games-fps/freedoom-data/freedoom-data-0.11.3.ebuild
new file mode 100644
index 00000000000..5e38d534c7e
--- /dev/null
+++ b/games-fps/freedoom-data/freedoom-data-0.11.3.ebuild
@@ -0,0 +1,29 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DESCRIPTION="Game resources for Freedoom: Phase 1+2"
+HOMEPAGE="https://freedoom.github.io"
+SRC_URI="https://github.com/freedoom/freedoom/releases/download/v${PV}/freedoom-${PV}.zip"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+BDEPEND="app-arch/unzip"
+
+S="${WORKDIR}/freedoom-${PV}"
+
+DOOMWADPATH=/usr/share/doom
+
+src_install() {
+ insinto ${DOOMWADPATH}
+ doins freedoom1.wad
+ doins freedoom2.wad
+ dodoc CREDITS.txt README.html
+}
+
+pkg_postinst() {
+ elog "Freedoom WAD files installed into ${DOOMWADPATH} directory."
+}
diff --git a/games-fps/freedoom-data/metadata.xml b/games-fps/freedoom-data/metadata.xml
new file mode 100644
index 00000000000..08a722785b1
--- /dev/null
+++ b/games-fps/freedoom-data/metadata.xml
@@ -0,0 +1,42 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <longdescription lang="en">
+ The Freedoom project aims to create a complete free content first person
+ shooter game. But Freedoom by itself is just the raw material for a
+ game: it must be paired with a compatible game engine to be played.
+
+ id Software released the source code to their classic game, Doom, under
+ the GNU General Public License. This means that the program code that
+ powers Doom is free; Freedoom complements this with free levels,
+ artwork, sound effects and music to make a completely free game.
+
+ Phase 1 is the first part of the single-player game, containing four
+ chapters which are nine levels each, smoothly paced for beginner
+ players. It is compatible with mods for the original Doom and The
+ Ultimate Doom.
+
+ Phase 2 is the second major part of the single-player game, a massive
+ 32-level chapter expanding upon the same concepts present in Phase 1, as
+ well as containing additional monsters and the double-barreled shotgun!
+ The levels in this game tend to demand more skillful play than the
+ previous chapters. It is compatible with mods for Doom II.
+ </longdescription>
+ <maintainer type="person">
+ <email>vilhelm.gray@gmail.com</email>
+ <name>William Breathitt Gray</name>
+ </maintainer>
+ <maintainer type="project">
+ <email>proxy-maint@gentoo.org</email>
+ <name>Proxy Maintainers</name>
+ </maintainer>
+ <maintainer type="project">
+ <email>games@gentoo.org</email>
+ <name>Gentoo Games Project</name>
+ </maintainer>
+ <upstream>
+ <bugs-to>https://github.com/freedoom/freedoom/issues</bugs-to>
+ <doc lang="en">https://freedoom.github.io</doc>
+ <remote-id type="github">freedoom/freedoom</remote-id>
+ </upstream>
+</pkgmetadata>
next reply other threads:[~2019-06-18 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 21:23 James Le Cuirot [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-05 20:11 [gentoo-commits] repo/gentoo:master commit in: games-fps/freedoom-data/ James Le Cuirot
2019-09-07 17:46 James Le Cuirot
2019-09-15 9:17 Mikle Kolyada
2019-10-12 14:29 James Le Cuirot
2019-11-07 21:28 James Le Cuirot
2019-11-07 21:28 James Le Cuirot
2020-10-01 15:29 James Le Cuirot
2021-03-05 23:12 James Le Cuirot
2021-07-07 12:23 Ionen Wolkens
2021-07-07 12:23 Ionen Wolkens
2021-07-29 11:06 Ionen Wolkens
2022-09-19 6:42 Michał Górny
2023-02-19 21:55 James Le Cuirot
2023-12-19 5:19 Sam James
2024-03-02 14:14 James Le Cuirot
2024-05-28 15:27 Michał Górny
2025-03-27 23:04 James Le Cuirot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1560892831.6d3f99b17a5f609a1ebc4330ab9cb7d9aef849b5.chewi@gentoo \
--to=chewi@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox