From: "Clément Lassieur" <clement@lassieur.org>
To: guix-devel@gnu.org
Subject: Firefox 52's end of life, packaging Icecat 60
Date: Thu, 12 Jul 2018 20:31:59 +0200 [thread overview]
Message-ID: <87efg8mhk0.fsf@lassieur.org> (raw)
Hello,
As this blog article[1] says, Firefox 52's end of life will happen on
August 28, 2018. That is, in 47 days. I imagine that by that time
Icecat 60 will be released, but it seems that we are pretty far from
being able to package it, because of the Rust packages that are needed.
There might be other technical difficulties that I'm not aware of,
though.
Is there any plan in this regard? Maybe, as a first step, we should
list the required dependencies so that people can pick them up? My
understanding of that article[2] is that the top level dependencies are
listed in Cargo.toml[3].
What is the current state of the Rust build system (cargo-build-system)?
Is there anything blocking that would prevent its use? I'm asking
because I see very few packages in gnu/packages/rust.scm.
Thank you,
Clément
[1]: https://blog.mozilla.org/futurereleases/2018/01/11/announcing-esr60-policy-engine/
[2]: https://developer.mozilla.org/en-US/Firefox/Building_Firefox_with_Rust_code
[3]: https://dxr.mozilla.org/mozilla-central/source/toolkit/library/rust/shared/Cargo.toml
next reply other threads:[~2018-07-12 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 18:31 Clément Lassieur [this message]
2018-07-13 10:22 ` Firefox 52's end of life, packaging Icecat 60 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
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=87efg8mhk0.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@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).