From: "Clément Lassieur" <clement@lassieur.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Firefox 52's end of life, packaging Icecat 60
Date: Tue, 31 Jul 2018 20:18:24 +0200 [thread overview]
Message-ID: <87o9en8e1b.fsf@lassieur.org> (raw)
In-Reply-To: <87bmanz5sd.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> Hi Clément,
[...]
> Thanks for looking into this, and for raising the issue. If you, or
> someone else, would like to take the lead on this, I would be grateful.
>
> For now, I would suggest trying to package upstream Firefox ESR 60.
> Although we cannot add Firefox itself to Guix, IceCat 60 will be almost
> identical to Firefox ESR 60, so we should be able to simply drop it in
> when it becomes available.
>
> To simplify things initially, you could comment out some or all of the
> patches, snippet code, configure flags, and phases which try to avoid
> bundled libraries and to use system libraries instead. However, I would
> not assume that commenting *all* of that out will help. It's possible
> that some of the bundled libraries won't work as-is on Guix because of
> our unusual filesystem layout, whereas our corresponding system
> libraries have already been patched to address those issues.
> Alternatively, any needed patches and/or substitutions from our system
> libraries could be applied to the corresponding bundled libraries.
>
> The 'link-libxul-with-libraries' phase could also be commented out
> temporarily, and instead you could manually set LD_LIBRARY_PATH as
> needed before launching Firefox, so that it can find the shared
> libraries it needs.
>
> Any of these temporary solutions would be fine for now. If you run into
> difficulties, I would be glad to take a look.
>
> If you can get Firefox ESR 60 working with the above simplifications,
> then I would be glad to work on avoiding the bundled libraries, adapting
> the 'link-libxul-with-libraries' phase, and swapping in IceCat 60.
>
> What do you think?
Thank you for your reply, it's very helpful. I'm still busy working on
Cuirass and then I'll need to take some vacations. I'll try to have a
look though, if I find some time.
Note that I have a powerful machine (it builds Firefox 52 in 8 minutes),
and I could temporarily give ssh access to someone working on
Firefox/Icecat if it helps.
Clément
prev parent reply other threads:[~2018-07-31 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 18:31 Firefox 52's end of life, packaging Icecat 60 Clément Lassieur
2018-07-13 10:22 ` Nils Gillmann
2018-07-29 9:11 ` Clément Lassieur
2018-07-31 17:14 ` Mark H Weaver
2018-07-31 18:18 ` Clément Lassieur [this message]
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=87o9en8e1b.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).