unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Vivien Kraus <vivien@planete-kraus.eu>, 50425@debbugs.gnu.org
Subject: [bug#50425] [PATCH] gnu: Add minetest-advtrains.
Date: Fri, 10 Sep 2021 18:26:35 +0200	[thread overview]
Message-ID: <021827be5ea5e4b1fe74555830d34c5b568a46c8.camel@telenet.be> (raw)
In-Reply-To: <f2ffd872759461a313a2449591830e19f90e565b.camel@planete-kraus.eu>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Hi,

Vivien Kraus schreef op vr 10-09-2021 om 14:46 [+0200]:
> > Maybe replace ‘realistic trains’ -> ‘realistic train system’,
> I’m not sure. Upstream really likes to use "train" as a general term,
> like in share/minetest/mods/advtrains/modpack.conf, the official
> description, the wiki, ... so I think it’s better to use that.
> 
Ok.

> > I think a linter will have something to say about long lines here
> > (try "./pre-inst-env guix lint minetest-advtrains minetest-basic-
> > trains").
> You’re right, I fixed the long lines and other warnings. However, I
> don’t know how to fix "no updater for minetest-xxx" for both minetest-
> advtrains and minetest-basic-trains. I can’t see a meaningful
> difference between my packages and the others.

There is no updater for mods from ContentDB at the moment, so this is
expected.  There's a patch series for allowing updating git-fetch
origins: <https://issues.guix.gnu.org/50072#0>.  Once (the final version of)
that patch series is merged, it should be feasible to add an updater
for mods from ContentDB.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-09-10 16:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  8:53 [bug#50425] [PATCH] gnu: Add minetest-advtrains Vivien Kraus via Guix-patches via
2021-09-06 11:02 ` Maxime Devos
2021-09-06 11:03   ` Maxime Devos
2021-09-06 11:17 ` Maxime Devos
2021-09-06 11:56   ` Vivien Kraus via Guix-patches via
2021-09-07 10:20     ` Maxime Devos
2021-09-07 10:45       ` Vivien Kraus via Guix-patches via
2021-09-10 10:25         ` Maxime Devos
2021-09-10 12:46           ` Vivien Kraus via Guix-patches via
2021-09-10 16:26             ` Maxime Devos [this message]
2021-09-16  8:03             ` Xinglu Chen
2021-09-16  8:36               ` Vivien Kraus via Guix-patches via
2021-09-16  8:39                 ` Vivien Kraus via Guix-patches via
2021-09-16 10:55                   ` Maxime Devos
2021-09-16 20:44                     ` bug#50425: " Ludovic Courtès

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=021827be5ea5e4b1fe74555830d34c5b568a46c8.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=50425@debbugs.gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).