Merge branch 'phyver:master' into devcontainer

Author: er2

.github/workflows/latest_game_archive.yml

@@ -4,12 +4,12 @@ on:
   push:
     branches:
       - "master"
-    tags-ignore:
-      - "*"
 
 jobs:
   pre-release:
+    name: "latest release"
     runs-on: "ubuntu-latest"
+
     steps:
       - name: "Checkout source code"
         uses: "actions/checkout@v4"

.gitignore

@@ -1,3 +1,4 @@
+Images/gsh-*-orig.gif
 tmp
 TODO
 .bin
@@ -8,8 +9,6 @@ TODO
 World
 locale/
 *~
-gameshell.sh
-gameshell-save.sh
-gameshell.tgz
-boxes-data.awk
+gameshell*
 game shell*
+boxes-data.awk

Dockerfile

@@ -11,7 +11,7 @@ RUN apt install --no-install-recommends --assume-yes \
     procps \
     nano \
     tree \
-    bsdmainutils \
+    ncal \
     x11-apps
 RUN apt clean
 RUN rm -rf /var/lib/apt/lists/*

Makefile

@@ -37,22 +37,22 @@ new: i18n/template.pot
 ## check that the auto.sh scripts work as expected
 check: clean
 	./utils/archive.sh -at -N "game shell (1)"
-	./"game shell (1).sh" -q -c 'gsh systemconfig; for _ in $$(seq 42); do gsh auto --abort < <(echo gsh); done; gsh stat'
+	./"game shell (1).sh" -q -c 'gsh systemconfig; for _ in $$(seq 50); do gsh auto --abort < <(echo gsh); done; gsh stat'
 
 ## check that the auto.sh scripts work as expected, in verbose mode
 check-verbose: clean
 	./utils/archive.sh -at -N "game shell (1)"
-	./"game shell (1).sh" -Dq -c 'gsh systemconfig; for _ in $$(seq 42); do gsh auto --abort; done; gsh stat'
+	./"game shell (1).sh" -Dq -c 'gsh systemconfig; for _ in $$(seq 50); do gsh auto --abort; done; gsh stat'
 
 ## run all the test.sh and auto.sh scripts
 tests-bash: clean
 	./utils/archive.sh -at -N "game shell (1)"
-	./"game shell (1).sh" -Bdq -c 'gsh systemconfig; for _ in $$(seq 42); do gsh goal|cat; gsh test --abort; gsh auto --abort; done; gsh stat'
+	./"game shell (1).sh" -Bdq -c 'gsh systemconfig; for _ in $$(seq 50); do gsh goal|cat; gsh test --abort; gsh auto --abort; done; gsh stat'
 
 ## run all the test.sh and auto.sh scripts
 tests-zsh: clean
 	./utils/archive.sh -at -N "game shell (1)"
-	./"game shell (1).sh" -Zdq -c 'gsh systemconfig; for _ in $$(seq 42); do gsh goal|cat; gsh test --abort; gsh auto --abort; done; gsh stat'
+	./"game shell (1).sh" -Zdq -c 'gsh systemconfig; for _ in $$(seq 50); do gsh goal|cat; gsh test --abort; gsh auto --abort; done; gsh stat'
 
 clean:
 	rm -rf i18n/*~ locale gameshell gameshell.tar gameshell.tgz gameshell.sh gameshell-save*.sh scripts/boxes-data.awk

README-fr.md

@@ -35,7 +35,7 @@ missions ont des dépendances additionnelles : elles seront annulées si leurs
 dépendances ne sont pas satisfaites. Sur Debian ou Ubuntu, lancez la commande
 suivante pour installer toutes les dépendances pour le jeu et les missions.
 ```sh
-$ sudo apt install gettext-base man-db psmisc nano tree bsdmainutils x11-apps
+$ sudo apt install gettext-base man-db psmisc nano tree ncal x11-apps
 ```
 Consultez le [manuel utilisateur](doc/user_manual.md) (en anglais) pour voir
 comment installer les dépendances sur d'autres systèmes (macOS, BSD, ...).

README-it.md

@@ -21,7 +21,7 @@ Come cominciare
 GameShell dovrebbe funzionare in qualunque sistema Linux standard, e anche su macOS e BSD (ma abbiamo eseguito pochi test su questi). Su Debian e Ubuntu, le uniche dipendenze (oltre `bash`) sono i pacchetti `gettext-base` e `awk`(questo di solito presente di default). Alcune missioni hanno dipendenze addizionali: queste missioni verranno saltate se le dipendenze non sono state risolte.
 Su Debian o Ubuntu, esegui i comandi seguenti per installare tutte le dipendenze del gioco e delle missioni.  
 ```sh
-$ sudo apt install gettext man-db procps psmisc nano tree bsdmainutils x11-apps wget
+$ sudo apt install gettext man-db procps psmisc nano tree ncal x11-apps wget
 ```
 Controlla il [manuale utente](doc/user_manual.md) per vedere come installare le dipendenze su altri sistemi (macOS, BSD, ...).
 

README.md

@@ -38,7 +38,7 @@ dependencies: these missions will be skipped if the dependencies are not met.
 On Debian or Ubuntu, run the following command to install all game and mission
 dependencies.
 ```sh
-$ sudo apt install gettext man-db procps psmisc nano tree bsdmainutils x11-apps wget
+$ sudo apt install gettext man-db procps psmisc nano tree ncal x11-apps wget
 ```
 Check the [user manual](doc/user_manual.md) to see how to install the game
 dependencies on other systems (macOS, BSD, ...).

doc/deps.md

@@ -20,14 +20,14 @@ the following
   - `pstree` (`psmisc` package in Debian/Ubuntu)
   - `nano` (`nano` package in Debian/Ubuntu)
   - `tree` (`tree` package in Debian/Ubuntu)
-  - `cal` (`bsdmainutils` package in Debian/Ubuntu)
+  - `cal` (`ncal` package in Debian/Ubuntu)
   - `xeyes` (`x11-apps` package in Debian/Ubuntu)
 
 On a Debian / Ubuntu system, the following ensures you have everything you
 need to run GameShell without problems.
 
 ```sh
-$ sudo apt install gettext-base man-db procps psmisc nano tree bsdmainutils x11-apps
+$ sudo apt install gettext-base man-db procps psmisc nano tree ncal x11-apps
 ```
 
 

doc/gameshell.md

@@ -139,14 +139,13 @@ You can customize the archive with the following options
   GameShell will ask for the player's name and email. This is useful in the
   classroom as it makes it easier to link a game to the corresponding student.
   (The player can run the archive in anonymous mode with the `-A` option.)
-* `--password PASSWORD`: you can choose the admin password for the archive.
+* `-p PASSWORD`: you can choose the admin password for the archive.
   This is also useful in the classroom as we might not want the students to
   learn of this password. :)
-* `-a`: keep the automatic scripts. Some missions come with a script that
-  automagically completes the missions. By default, those scripts are **not**
-  included in the archive. Use `-a` if you want to keep them.
 * `-N NAME`: if you want the archive and its directory to be called something
   other than "GameShell", you can set the name with this option.
-* `-k`: keep the GameShell archive. The compressed `tar` archive is appended
-  to a shell script to create the executable archive. With this option, you
-  can keep the "standard" `tar` archive as well as the executable one.
+
+More options are available and listed in the output of
+```sh
+$ ./utils/archive.sh -h
+```

doc/mission.md

@@ -442,13 +442,13 @@ which make testing easier.
 Those files are not included in GameShell archives.
 
 
-Adding the mission to the `index.txt` file
-----------------------------------------
+Adding the mission to the `default.idx` file
+------------------------------------------
 
 When run without arguments GameShell will get the list of mission from the
-file `$GSH_ROOT/missions/index.txt`.
+file `$GSH_ROOT/missions/default.idx`.
 
-You can give a list of `index.txt` files and mission directories as arguments
+You can give a list of `default.idx` files and mission directories as arguments
 of GameShell if you want to customize the list / order of missions. This is
 particularly useful when testing a new mission:
 ```sh
@@ -464,7 +464,7 @@ Dummy missions
 
 "Dummy" missions are used to share data between missions. A mission is "dummy"
 * either when it doesn't contain a `check.sh` script,
-* or it is listed with a "`!`" in front of its name in the `index.txt` file.
+* or it is listed with a "`!`" in front of its name in the `default.idx` file.
 
 A dummy mission is used during the initialisation phase, so that it can
 contain a `static.sh` file. It can for example be used to share executable
@@ -483,7 +483,7 @@ cp "$MISSION_DIR/../00_shared/ascii-art/elephant.txt" "$GSH_HOME/Jungle/"
 ```
 
 _Note:_ don't forget to include dummy missions in the corresponding
-`index.txt` file, or it won't be included in GameShell executable archives by
+`default.idx` file, or it won't be included in GameShell executable archives by
 default.