Github messages for voidlinux
 help / color / mirror / Atom feed
From: Zapeth <Zapeth@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: firefox-esr: update to 102.6.0
Date: Thu, 22 Dec 2022 20:12:55 +0100	[thread overview]
Message-ID: <20221222191255.uiFGzV4W-qswngbuVjBbuAZ7vuSjiwOkJFub0lF4Zk0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41060@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

New comment by Zapeth on void-packages repository

https://github.com/void-linux/void-packages/pull/41060#issuecomment-1363216129

Comment:
I managed to make some space on my machine and was able to build `firefox-esr` and `firefox-esr-i18n` (the only issue I came across was a language entry not being ordered correctly which caused checksum issues, but thats fixed now)

I also had to update my system packages due to the recent gcc update, but after that I was able to use the new version (briefly tested it, updated PR description)

> @Zapeth Looking over the template I cant find that files/mozconfig is being sourced anymore, can we stop vendoring it since add_options are defined in template?

I think so, yes. I compared the add_options and the only difference I found was that `--enable-system-ffi` is now set with `--with-system-ffi`. I don't know which of the two should be set, but I'd keep the latter since its also used in the normal `firefox` package.

I went ahead and removed it, also rebased again


  parent reply	other threads:[~2022-12-22 19:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 14:23 [PR PATCH] " Zapeth
2022-12-13 17:44 ` [PR PATCH] [Updated] " Zapeth
2022-12-13 17:51 ` Zapeth
2022-12-13 18:42 ` [PR PATCH] [Updated] " Zapeth
2022-12-13 21:30 ` Zapeth
2022-12-14 10:11 ` biopsin
2022-12-14 10:15 ` biopsin
2022-12-14 13:42 ` [PR PATCH] [Updated] " Zapeth
2022-12-14 13:50 ` Zapeth
2022-12-14 15:01 ` [PR PATCH] [Updated] " Zapeth
2022-12-14 15:03 ` Zapeth
2022-12-14 17:16 ` biopsin
2022-12-14 17:32 ` paper42
2022-12-14 18:35 ` [PR PATCH] [Updated] " Zapeth
2022-12-14 18:39 ` Zapeth
2022-12-21 20:15 ` [PR PATCH] [Updated] " Zapeth
2022-12-22  9:18 ` biopsin
2022-12-22 18:08 ` [PR PATCH] [Updated] " Zapeth
2022-12-22 18:32 ` Zapeth
2022-12-22 19:12 ` Zapeth
2022-12-22 19:12 ` Zapeth [this message]
2022-12-22 23:36 ` biopsin
2022-12-31 16:36 ` paper42
2022-12-31 16:55 ` [PR PATCH] [Updated] " Zapeth
2023-01-18 11:18 ` Zapeth
2023-01-18 11:27 ` Zapeth
2023-01-21 10:08 ` firefox-esr: update to 102.7.0 biopsin
2023-01-21 10:26 ` Zapeth
2023-01-21 12:22 ` biopsin
2023-03-05  9:28 ` biopsin
2023-03-05 16:50 ` Zapeth
2023-03-05 16:55 ` Zapeth
2023-04-11 14:07 ` [PR PATCH] [Closed]: " Zapeth

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=20221222191255.uiFGzV4W-qswngbuVjBbuAZ7vuSjiwOkJFub0lF4Zk0@z \
    --to=zapeth@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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. 
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 NNTP newsgroup(s).