Hemiptera Bugtracker at bugs.linux-forks.de

186@bugs.linux-forks.de schreef op vr 10-09-2021 om 21:08 [+0200]:

> Thanks for the info. I've adjusted it accordingly.

> Is there something I can do to ease the Guix package maintaining (such as adding a

> branch that always points to the latest stable release)?

Guix only needs the information on ContentDB to be complete. Currently, it is complete,

except for the git commit. It doesn't seem like a ‘stable branch’ would be of any use.

There are a few things you can do, however:

- Include the commit the release was made with on ContentDB. Currently, Guix uses

the git repository (and not the zips provided by ContentDB) and needs to know the

commit. As the commit is unknown by Guix, someone had to manually find out

which commit to use when packaging advtrains.

Guix also has automatic updaters, e.g. for pypi, hackage, ... (there is one for

Minetest mods on ContentDB, but it's not yet merged and needs some changes).

The updater for mods on ContentDB needs the commit of the latest release, so it

would be useful if ContentDB includes the commit for advtrains.

- Keep using version numbers as release titles.

Guix packages need a version number. Many mods on ContentDB don't have one,

or do have version numbers but the latest release on ContentDB is ahead of the

latest version ... This can be worked around, but it's much more convenient

if the mod uses version numbers.

Also, the related orwell/basic_trains mod still has the ‘AGPL-3.0-only’ license

listed on <https://content.minetest.net/packages/orwell/basic_trains/> instead

of ‘AGPL-3.0-or-later’. Presumably the other mods under your name at

<https://content.minetest.net/users/orwell/> need their license information

adjusted a well?

- maxime

advtrains