From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 50700-done@debbugs.gnu.org
Subject: bug#50700: [PATCH] import/minetest: Define an updater for mods on ContentDB.
Date: Sat, 02 Oct 2021 17:18:08 +0200 [thread overview]
Message-ID: <8735pjwj4f.fsf@gnu.org> (raw)
In-Reply-To: <84d7e4dbcf5e472cded21c9f72c8673b0dbf9064.camel@telenet.be> (Maxime Devos's message of "Mon, 20 Sep 2021 15:38:36 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> From fa4130e7fe96fc884adcf0d30d222c6bbe26e1e9 Mon Sep 17 00:00:00 2001
> From: Maxime Devos <maximedevos@telenet.be>
> Date: Mon, 20 Sep 2021 15:27:08 +0200
> Subject: [PATCH] import/minetest: Define an updater for mods on ContentDB.
>
> Only detecting updates is currently supported. To actually
> perform the uppdates, a patch like
> <https://issues.guix.gnu.org/50072#4> is required.
>
> * guix/import/minetest.scm
> (version-style,minetest-package?,latest-minetest-release): New procedures.
> (%minetest-updater): New updater.
> * tests/minetest.scm
> (upstream-source->sexp,expected-sexp,example-package): New procedure.
> (test-release,test-no-release): New macro's.
> ("same version","new version (dotted)","new version (date)")
> ("new version (git -> dotted)","dotted->date","date->dotted")
> ("no commit informaton, no new release")
> ("minetest is not a minetest mod")
> ("technic is a minetest mod")
> ("upstream-name is required"): New tests.
I only skimmed it for stylistic issues and trust you for the actual
functionality. :-)
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2021-10-02 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 13:38 [bug#50700] [PATCH] import/minetest: Define an updater for mods on ContentDB Maxime Devos
2021-10-02 15:18 ` Ludovic Courtès [this message]
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=8735pjwj4f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50700-done@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).