unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>, <56852@debbugs.gnu.org>
Subject: [bug#56852] [PATCH] gnu: Add exult.
Date: Sun, 31 Jul 2022 15:23:13 +0100	[thread overview]
Message-ID: <CLTWQV98YDW4.142L9O3SZZBNO@guix-aspire> (raw)
In-Reply-To: <20220731104635.31835-1-me@tobias.gr>

I just thought of some more possible improvements:

On Sun Jul 31, 2022 at 11:46 AM BST, Tobias Geerinckx-Rice via Guix-patches via wrote:
> +                   "--enable-exult-studio"
Couldn't this go in a new `exult:studio` output?

> +                   "--enable-compiler"
I'm not sure what this compiler is, but if it's a separate program I guess it could
use `exult:compiler`.

> +                   "--enable-gimp-plugin"
And this could go in `exult:gimp`.

> +                   (substitute* "gamemgr/modmgr.cc"
> +                     ;; EXULT_DATADIR is in the store where it's rather hard for
> +                     ;; users to put game assets.  Use a more writable home by
> +                     ;; default, which users can override in their ~/.exult.cfg.
> +                     (("<GAMEHOME>")
> +                      (string-append "<HOME>/.local/share/exult"))
> +                     ;; …however, this causes a regression: the mods which we'll
> +                     ;; install to EXULT_DATADIR are no longer found.  So: don't
> +                     ;; look for mods alongside the assets by default.  This too
> +                     ;; can be overridden in users' ~/.exult.cfg.
> +                     (("game_path( \\+ \"/mods\")" _ +suffix)
> +                      (string-append "get_system_path(\"<GAMEHOME>/\") + "
> +                                     "cfgname" +suffix))))))))
Perhaps we could patch in a GUIX_EXULT_PATH env var so we can add a search path for
packaging mods.

    -- (




  parent reply	other threads:[~2022-07-31 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 10:46 [bug#56852] [PATCH] gnu: Add exult Tobias Geerinckx-Rice via Guix-patches via
2022-07-31 11:52 ` ( via Guix-patches via
2022-07-31 13:26   ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-31 13:41     ` ( via Guix-patches via
2022-07-31 14:31     ` Maxime Devos
2022-07-31 14:23 ` ( via Guix-patches via [this message]
2022-08-12 19:46   ` Tobias Geerinckx-Rice via Guix-patches via
2023-09-02  3:38 ` bug#56852: " Vagrant Cascadian

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=CLTWQV98YDW4.142L9O3SZZBNO@guix-aspire \
    --to=guix-patches@gnu.org \
    --cc=56852@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=paren@disroot.org \
    /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).