unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 67848@debbugs.gnu.org
Subject: bug#67848: [PATCH] WIP: gnu: icedove: Update to 115.5.2.
Date: Sun, 17 Dec 2023 17:02:20 -0500	[thread overview]
Message-ID: <87msu87aj7.fsf@gmail.com> (raw)
In-Reply-To: <f6c2d3cf226581d2711af56aca62b840bb26e736.1702728928.git.jonathan.brielmaier@web.de> (Jonathan Brielmaier's message of "Sat, 16 Dec 2023 13:17:39 +0100")

Hi Jonathan,

Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:

> * gnu/packages/gnuzilla.scm (all-mozilla-102-locales,
> %icecat-102-base-version, %icecat-102-version, icecat-102-source):
> Remove variables.
> (%icedove-build-id, %icedove-version, thunderbird-comm-source): Update for 115.5.2.
> (thunderbird-comm-l10n): Switch to provided tarball.
> (icedove-source)[origin]: Add `zstd` package. Use `icecat-source`.
> Provide l10n folder from tarball.
> (icedove-minimal)[arguments]: Use MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE instead
> of deprecated MACH_USE_SYSTEM_PYTHON. Use GUIX_PYTHONPATH and bundled
> NSS library.
> [inputs]: Use `icu4c-73-promise`. Add `nspr`. Remove `nss` for now.

Thanks for working on this!

I don't think it's acceptable to reintroduce bundling for NSS, unless we
have strong reasons to.  We should rather introduce a new NSS variant at
a sufficient version in a prior commit.  NSS takes time to build, but
otherwise shouldn't be too difficult, if I recall correctly my
experience doing it.

-- 
Thanks,
Maxim





       reply	other threads:[~2023-12-17 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f6c2d3cf226581d2711af56aca62b840bb26e736.1702728928.git.jonathan.brielmaier@web.de>
2023-12-17 22:02 ` Maxim Cournoyer [this message]
2023-12-18 17:27   ` bug#67848: [PATCH] WIP: gnu: icedove: Update to 115.5.2 Jonathan Brielmaier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-19 16:40     ` Maxim Cournoyer

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87msu87aj7.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=67848@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    /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/emacs.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).