From: Marius Bakke <mbakke@fastmail.com>
To: guix-devel@gnu.org
Subject: State of ungoogled-chromium in Guix
Date: Wed, 23 Oct 2019 22:00:51 +0200 [thread overview]
Message-ID: <87v9sfut8s.fsf@devup.no> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 713 bytes --]
Hello Guix,
Version 78 of the upstream Chromium project was released yesterday, with
the usual amount of security fixes:
https://chromereleases.googleblog.com/2019/10/stable-channel-update-for-desktop_22.html
Unfortunately the 'ungoogled-chromium' variant in Guix is still stuck on
version 76. The reason is that we rely on Debians patches, which have
gone stale:
https://salsa.debian.org/chromium-team/chromium
I plan to remove 'ungoogled-chromium' and 'ungoogled-chromium-wayland'
in a few days, unless someone is willing to port the patches. I can
help extracting just the few changes we need, but do not have time nor
motivation to port them to the newer version myself.
Here is a preliminary patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: diff --]
[-- Type: text/x-patch, Size: 1396 bytes --]
diff --git a/gnu/packages/chromium.scm b/gnu/packages/chromium.scm
index aad1fd9203..21fc3625a6 100644
--- a/gnu/packages/chromium.scm
+++ b/gnu/packages/chromium.scm
@@ -42,6 +42,7 @@
#:use-module (gnu packages gl)
#:use-module (gnu packages glib)
#:use-module (gnu packages gnome)
+ #:use-module (gnu packages gnuzilla)
#:use-module (gnu packages gperf)
#:use-module (gnu packages gtk)
#:use-module (gnu packages icu4c)
@@ -806,7 +807,8 @@ from forcing GEXP-PROMISE."
;; Building Chromium takes ... a very long time. On a single core, a busy
;; mid-end x86 system may need more than 24 hours to complete the build.
- (properties '((timeout . 144000))) ;40 hours
+ (properties '((timeout . 144000) ;40 hours
+ (hidden? . #t)))
(home-page "https://github.com/Eloston/ungoogled-chromium")
(description
@@ -852,3 +854,9 @@ disabled in order to protect the users privacy.")
(assoc-ref %build-inputs "wayland")
"/bin/wayland-scanner\""))
(delete "use_vaapi=true" ,flags)))))))
+
+(define-public ungoogled-chromium-is-deprecated
+ (deprecated-package "ungoogled-chromium" icecat))
+
+(define-public ungoogled-chromium-wayland-is-deprecated
+ (deprecated-package "ungoogled-chromium-wayland" icecat))
[-- Attachment #1.3: Type: text/plain, Size: 11 bytes --]
Thoughts?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2019-10-23 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:00 Marius Bakke [this message]
2019-10-24 22:03 ` State of ungoogled-chromium in Guix Tobias Geerinckx-Rice
2019-10-25 20:40 ` Ludovic Courtès
2019-11-03 18:46 ` Marius Bakke
2019-11-04 14:41 ` Ludovic Courtès
2019-11-10 20:16 ` Vagrant Cascadian
2019-11-10 22:56 ` Marius Bakke
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=87v9sfut8s.fsf@devup.no \
--to=mbakke@fastmail.com \
--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).