From: Maxime Devos <maximedevos@telenet.be>
To: 53144@debbugs.gnu.org
Cc: Maxime Devos <maximedevos@telenet.be>
Subject: [bug#53144] [PATCH 05/13] gnu: minetest: Remove obsolete comments about version numbers.
Date: Sun, 9 Jan 2022 19:10:07 +0000 [thread overview]
Message-ID: <20220109191015.33058-5-maximedevos@telenet.be> (raw)
In-Reply-To: <20220109191015.33058-1-maximedevos@telenet.be>
According to the new contributing documentation about Minetest,
the release titles from ContentDB are acceptable.
* gnu/packages/minetest.scm
(minetest-basic-materials,minetest-coloredwood,minetest-homedecor-modpack)
(minetest-mobs,minetest-mobs-animal,minetest-pipeworks,minetest-technic):
Remove comments about version numbers / dates.
---
gnu/packages/minetest.scm | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/gnu/packages/minetest.scm b/gnu/packages/minetest.scm
index cdf862e189..8ade7bb966 100644
--- a/gnu/packages/minetest.scm
+++ b/gnu/packages/minetest.scm
@@ -211,7 +211,6 @@ (define-public minetest-moreores
(define-public minetest-basic-materials
(package
(name "minetest-basic-materials")
- ;; Upstream uses dates as version numbers.
(version "2021-12-26")
(source
(origin
@@ -240,7 +239,6 @@ (define-public minetest-basic-materials
(define-public minetest-coloredwood
(package
(name "minetest-coloredwood")
- ;; Upstream uses dates as version numbers.
(version "2021-04-14-1")
(source
(origin
@@ -292,8 +290,6 @@ (define-public minetest-ethereal
(define-public minetest-homedecor-modpack
(package
(name "minetest-homedecor-modpack")
- ;; Upstream doesn't tag releases, so use the release title from
- ;; ContentDB as version.
(version "2021-12-26")
(source
(origin
@@ -379,8 +375,6 @@ (define-public minetest-mineclone
(define-public minetest-mobs
(package
(name "minetest-mobs")
- ;; Upstream does not tag release, so use the ContentDB release
- ;; title instead.
(version "2021-12-12")
(source
(origin
@@ -408,8 +402,6 @@ (define-public minetest-mobs
(define-public minetest-mobs-animal
(package
(name "minetest-mobs-animal")
- ;; Upstream does not use version numbers, so use the release title
- ;; from ContentDB instead;
(version "2021-11-14")
(source
(origin
@@ -435,7 +427,6 @@ (define-public minetest-mobs-animal
(define-public minetest-pipeworks
(package
(name "minetest-pipeworks")
- ;; Upstream uses dates as version numbers.
(version "2021-04-14-1")
(source
(origin
@@ -466,8 +457,6 @@ (define-public minetest-pipeworks
(define-public minetest-technic
(package
(name "minetest-technic")
- ;; Upstream doesn't keep version numbers, so use the release
- ;; date on ContentDB instead.
(version "2021-09-11")
(source
(origin
@@ -604,8 +593,6 @@ (define-public minetest-unifieddyes
(define-public minetest-unified-inventory
(package
(name "minetest-unified-inventory")
- ;; Upstream doesn't keep version numbers, so use the release title
- ;; on ContentDB instead.
(version "2021-12-26")
(source
(origin
--
2.34.0
next prev parent reply other threads:[~2022-01-09 19:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 19:08 [bug#53144] [PATCH 0/13] Make more git-using packages auto-updatable Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 01/13] doc: Give some tips on Minetest packaging Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 02/13] gnu: minetest-ethereal: Follow new versioning conventions Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 03/13] gnu: minetest-mesecons: " Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 04/13] gnu: minetest-throwing: " Maxime Devos
2022-01-09 19:10 ` Maxime Devos [this message]
2022-01-09 19:10 ` [bug#53144] [PATCH 06/13] gnu: minetest-ethereal: Update to 2022-01-05 Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 07/13] gnu: minetest-mesecons: Update to 2021-11-28 Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 08/13] gnu: minetest-mobs: Update to 2022-01-03 Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 09/13] doc: Document the Minetest importer Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 10/13] upstream: Support incrementing the revision of 'git-version' Maxime Devos
2022-01-18 17:33 ` [bug#53144] [PATCH 0/13] Make more git-using packages auto-updatable Ludovic Courtès
2022-01-09 19:10 ` [bug#53144] [PATCH 11/13] git: Support resolving references without cloning Maxime Devos
2022-01-18 17:39 ` [bug#53144] [PATCH 0/13] Make more git-using packages auto-updatable Ludovic Courtès
2022-04-03 11:47 ` Maxime Devos
2022-01-09 19:10 ` [bug#53144] [PATCH 12/13] import: Add 'latest-git' updater Maxime Devos
2022-01-18 17:45 ` [bug#53144] [PATCH 0/13] Make more git-using packages auto-updatable Ludovic Courtès
2022-01-09 19:10 ` [bug#53144] [PATCH 13/13] gnu: minetest-throwing-arrows: Use 'latest-git' updater Maxime Devos
2022-01-09 21:15 ` [bug#53144] [PATCH 01/13] doc: Give some tips on Minetest packaging Liliana Marie Prikler
2022-01-09 23:29 ` Maxime Devos
2022-01-10 21:29 ` Liliana Marie Prikler
2022-01-18 17:30 ` [bug#53144] [PATCH 0/13] Make more git-using packages auto-updatable Ludovic Courtès
[not found] ` <handler.53144.B.164175531629466.ack@debbugs.gnu.org>
2022-01-09 19:49 ` [bug#53144] Acknowledgement ([PATCH 0/13] Make more git-using packages auto-updatable) Maxime Devos
2022-06-06 15:15 ` [bug#53144] [PATCH 0/13] Make more git-using packages auto-updatable Maxime Devos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220109191015.33058-5-maximedevos@telenet.be \
--to=maximedevos@telenet.be \
--cc=53144@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).