From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61387@debbugs.gnu.org
Subject: bug#61387: 30.0.50; Support webkit2gtk-4.1
Date: Thu, 09 Feb 2023 15:19:37 +0100 [thread overview]
Message-ID: <ua61mhqfa@gentoo.org> (raw)
In-Reply-To: <83zg9nkkym.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Feb 2023 15:49:21 +0200")
>>>>> On Thu, 09 Feb 2023, Eli Zaretskii wrote:
> Are you proposing this for Emacs 29 or for Emacs 30?
Emacs 30, because I thought that it was to late for it to land in the
emacs-29 branch? If it could be included in Emacs 29, I would prefer
that.
>> The patch below adds a configure option --with-webkit2gtk=VALUE that
>> allows to select version 4.0 or 4.1.
> Is it really necessary to ask for a specific version? Why cannot
> Emacs use the version that is installed?
That could be done as a fallback, but a configure switch is still
needed. Think of a package for a distro, which has to include the
information whether webkit2gtk-4.0 or 4.1 have to be pulled in as
a dependency. There, Emacs has to be built against a well-defined
version, even if both versions of webkit2 are installed on the build
system (for Gentoo, that will be the case for some transition time).
Should I update the patch to allow 3 values "4.0", "4.1", and "auto",
with "auto" being the default? And in the default case, should it
check for 4.0 or 4.1 first?
next prev parent reply other threads:[~2023-02-09 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 11:52 bug#61387: 30.0.50; Support webkit2gtk-4.1 Ulrich Müller
2023-02-09 12:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 13:49 ` Eli Zaretskii
2023-02-09 14:19 ` Ulrich Mueller [this message]
2023-02-09 15:41 ` Eli Zaretskii
2023-02-09 15:54 ` Ulrich Müller
2023-02-10 2:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10 5:27 ` Ulrich Müller
2023-02-12 9:40 ` Ulrich Müller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ua61mhqfa@gentoo.org \
--to=ulm@gentoo.org \
--cc=61387@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.