[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#28004] Chromium
From: |
ng0 |
Subject: |
[bug#28004] Chromium |
Date: |
Fri, 12 Jan 2018 09:38:19 +0000 |
Marius Bakke transcribed 2.3K bytes:
> ng0 <address@hidden> writes:
>
> > Marius Bakke transcribed 39K bytes:
> >
> >> Testing and feedback welcome!
> >>
> >> Currently there are two "important" (blocking?) TODOs left:
> >>
> >> * Move the 'delete-bundled-software' phase to a source snippet.
> >> Repacking the ~500MiB compressed tarball is *really* expensive. It
> >> should also aid the licensing situation.
> >> * Delete the two default entries from the "most used" list on the New
> >> Tab page. The first run will download thumbnails for these sites,
> >> leaking data. One of them also leads to the disabled-by-default
> >> store, promoting non-free software.
> >>
> >> I'm optimistic that fixing the second item will make the browser not
> >> leak *any* data at launch with the default configuration. Which leads
> >> to a third item: writing a system test that verifies that launching
> >> Chromium does indeed not initiate any network traffic.
> >>
> >> Anyway, here is the latest patch:
> >>
> >
> >> From f813b2d7ec0728a906720fa74bf9f442af6ab10d Mon Sep 17 00:00:00 2001
> >> From: Marius Bakke <address@hidden>
> >> Date: Wed, 12 Oct 2016 17:25:05 +0100
> >> Subject: [PATCH] gnu: Add chromium.
> >>
> >> * gnu/packages/chromium.scm: New file.
> >> * gnu/local.mk: Record it.
> >
> > I think you forgot a package:
> >
> > gnu/packages/chromium.scm:664:5: icu4c-59.1: unbound variable
>
> Indeed. This can now be changed to use the regular "icu4c" package.
Okay, will change. Thanks!
> Tangentially, these kinds of problems are typical with new Chromium
> releases. In 63 or later, system harfbuzz had to be disabled. If we
> are going to carry this package, changes like these *will* be normal.
>
> Upstream only tests their releases with Clang, and with the bundled
> versions of packages, regardless of the unbundling script. Not great.
Yeah. I've been there, and read the frustration of other packagers
when I worked on getting a basic skeleton of chromium + dependencies
ready one(?) year ago.
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is/a/ :: https://ea.n0.is
signature.asc
Description: PGP signature
- [bug#28004] Chromium, (continued)
- [bug#28004] Chromium, Ludovic Courtès, 2018/01/16
- [bug#28004] Chromium, Marius Bakke, 2018/01/16
- [bug#28004] Chromium, Tobias Geerinckx-Rice, 2018/01/16
- [bug#28004] Chromium, Marius Bakke, 2018/01/16
- [bug#28004] Chromium, Leo Famulari, 2018/01/16
- [bug#28004] Chromium, Ludovic Courtès, 2018/01/17
- [bug#28004] Chromium, Mike Gerwitz, 2018/01/17
- [bug#28004] Chromium, ng0, 2018/01/16
[bug#28004] Chromium, ng0, 2018/01/09