builds fine and runs! merging! thanks for the contribution!

This needs export GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 to prevent a wall of warnings during install. I've commited that and various style fixes in 3dded41.

I expect the authors of pull requests to explain why git revision is not the tag with the version, especially when it differs from the tag with the version; but in this case it seems somewhat acceptable.

I expect the authors of pull requests to explain why git revision is not the tag with the version, especially when it differs from the tag with the version; but in this case it seems somewhat acceptable.

For posterity: The reason is because gtetrinet hasn't been actively maintained since about a decade ago, and some fixes we need (like https://github.com/GNOME/gtetrinet/commit/717dc612a884011ec1c0e838db1c9c51b9e533c6) happened in the last few years but never made it into a new release version.

@orivej I put a line break in the argument list because the manual says

Function formal arguments are written as:

{ arg1, arg2, arg3 }:

but if they don't fit on one line they're written as:

{ arg1, arg2, arg3
, arg4, ...
, # Some comment...
  argN
}:

It doesn't say how many characters consistutes "one line," so I guessed 80. Is that wrong? I'll PR to update the docs if I can find out what the correct style is.

Your indentation was fine, but I removed some dependencies and the list got shorter. (Some dependencies are subsumed by autoreconfHook, perl is an internal dependency of intltool and is not directly used by gtetrinet.)

Ah yes, sorry I misread.

Regarding the warning output, would you mind explaining why it matters (and should we mention that in the manual, perhaps in the Contributing guide?), and how did you know to set the GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL variable to fix it?

The warnings are just inconvenient: for example, if someone changes a dependency of gtetrinet and tests all affected packages with nox-review, they may waste some time to check if the warnings are relevant or not, because they are very prominent; and they make any previous output hard to read, because they quickly scroll it away.

I've looked for how other packages deal with grome2.GConf (maybe there is a way to actually install the schemas to avoid the warnings?) and found this variable used here: