From: Jesse Gibbons <jgibbons2357@gmail.com>
To: 52913@debbugs.gnu.org
Subject: bug#52913: 0ad only builds fine with a specific version of mozjs
Date: Sat, 1 Jan 2022 12:14:18 -0700 [thread overview]
Message-ID: <5491e57c-ae88-aa24-256b-c7d6f038cba2@gmail.com> (raw)
In-Reply-To: <87y241azi0.fsf@kitej>
> What would be the best way to fix this?
> - keep a mozjs-78.6 package around just for 0ad
> - patch 0ad to fix the compatibility issues with mozjs 78.15
> - use the mozjs version bundled in the 0ad sources
>
> WDYT?
Keeping mozjs-78.6 just for 0ad will probably make things harder later
on because it's another package to maintain and users likely won't be
able install 0ad and icecat/icedove in the same profile. I suppose users
can always use `-P /path/to/0ad-profile` when installing or updating 0ad.
I'm thinking using the bundled mozjs is perhaps the best option, though
it isn't particularly guixy, because I expect most users would want the
0ad packaged by guix to be compatible with other 0ad builds in the wild.
However, I think it would be useful to fix compatibility issues with
mozjs 78.15 so interested contributors can tell upstream if guix's
current minor version breaks the expected deterministic behaviors
described in the error.
Another option would be to keep mozjs-78.6 for 0ad and patch it so
interested users can test updated mozjs using
`--with-input=mozjs=mozjs`. It isn't very difficult to modify a list of
packages to use a specific mozjs in a manifest or home configuration,
right? Though I guess interested contributors could always add the patch
themselves just as easily...
Anyway, that's my two cents.
next prev parent reply other threads:[~2022-01-01 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 9:17 bug#52913: 0ad only builds fine with a specific version of mozjs Guillaume Le Vaillant
2022-01-01 19:14 ` Jesse Gibbons [this message]
2022-01-01 20:27 ` Liliana Marie Prikler
2022-01-02 12:56 ` Guillaume Le Vaillant
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=5491e57c-ae88-aa24-256b-c7d6f038cba2@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=52913@debbugs.gnu.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).