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: Tue, 07 Sep 2021 12:20:58 +0200	[thread overview]
Message-ID: <f43eb8064e9e5e06c29a87194faaf7e787ee9721.camel@telenet.be> (raw)
In-Reply-To: <b4c0387688c3197484f96ea46f2c800b64b77faf.camel@planete-kraus.eu>

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

Vivien Kraus schreef op ma 06-09-2021 om 13:56 [+0200]:
> Hello Maxime,
> 
> Le lundi 06 septembre 2021 à 13:17 +0200, Maxime Devos a écrit :
> > Did the minetest importer work well for you?
> I noticed 3 minor things:
> 1. The advtrain dependency on basic-trains was duplicated, I had to
> remove one occurence;

I can reproduce this with ‘guix import minetest --recursive orwell/basic_trains’.
Presumably the issue is that advtrains is listed twice in the dependencies
on ContentDB, as ‘advtrains’ and ‘advtrains_train_track’.  I'll send a patch
to remove duplicates.

> 2. The version number came prefixed with a "v" that I had to remove;

The importer uses the ‘release title’ as version number.  Apparently
the release titles for orwell/advtrains include a "v" prefix.  I'll
send a patch to remove the prefix.

> 3. It was not able to get the commit ID and the hash for minetest-
> advtrains, I had to fill it in myself (it was set to #f). Presumably
> because of the exotic tag name.

FWIW, the minetest importer doesn't look at git tag names, it just copies
the commit from ContentDB.  And in case of advtrains, the commit is
not available there, so the importer sets it to #false.
<https://content.minetest.net/api/packages/orwell/advtrains/releases/>.

> [...]
> 
> Also, when I run ./etc/indent-code.el gnu/packages/minetest, there are
> some re-indentations that happen for othe minetest packages. Thus, I’m
> not sure what indentation and general style I should adopt. Hopefully
> this problem will be fixed by guix style :)

The indentation from "./etc/indent-code.el" should be good.  Feel free
to precedede the ‘gnu: Add minetest-advtrains’ patch with a patch fixing
the indentation.

Greetings,
Maime.

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

  reply	other threads:[~2021-09-07 10:22 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 [this message]
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
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=f43eb8064e9e5e06c29a87194faaf7e787ee9721.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).