[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Firefox 52's end of life, packaging Icecat 60

From: Nils Gillmann
Subject: Re: Firefox 52's end of life, packaging Icecat 60
Date: Fri, 13 Jul 2018 10:22:18 +0000

Clément Lassieur transcribed 1.1K bytes:
> 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.

As far as my experience with trying to finish newer firefox packages
goes, you can use cendor bundled crates. My idea so far was something
along thoe lines (not succesful so far):

;; (add-before 'configure 'unpatch-sh
;;   (lambda _
;;     (substitute* (list 
;;       (((string-append "^#!" (which "sh")))
;;        "#!/bin/sh"))
;;     #t))
(add-after 'patch-source-shebangs 'patch-cargo-checksums
  (lambda* (#:key inputs #:allow-other-keys)
;; third_party/rust/ has no Cargo.lock, but all the checksum.json files
;; Cargo.lock files occur outside of third_party/rust/ though.
;; (for-each
;;  (lambda (filename)
;;    (substitute* "Cargo.lock"
;;      (("(\"checksum .* = )\".*\"" all name)
;;       (string-append name "\"" ,%cargo-reference-hash "\""))))
;;  (find-files "third_party/rust" filename))
(lambda (filename)
(use-modules (guix build cargo-build-system))
(delete-file filename)
(let* ((dir (dirname filename)))
(display (string-append
"patch-cargo-checksums: generate-checksums for "
dir "\n"))
(generate-checksums dir ,%cargo-reference-project-file)))
(find-files "third_party/rust" ".cargo-checksum.json"))

I'm more concerned about the unreliable building of rust itself.
A handful of us tried to build the new version and for some it
failed (in the testsuite), for some it succeeded.

> 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)?

the inofficcial (no bug filed) guidelines:

> Is there anything blocking that would prevent its use?  I'm asking

Depends on what you want to use, but it is far from good enough for "real"
applications (like 200 crates dependencies).

> because I see very few packages in gnu/packages/rust.scm.
> Thank you,
> Clément
> [1]: 
> [2]: 
> [3]: 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]