From: Marius Bakke <marius@gnu.org>
To: 44335@debbugs.gnu.org
Subject: [bug#44335] [PATCH 0/2] Install Chromium extensions with Guix!
Date: Fri, 30 Oct 2020 19:29:25 +0100 [thread overview]
Message-ID: <20201030182925.5151-1-marius@gnu.org> (raw)
Greetings Guix,
These patches lay the groundwork for packaging Chromium extensions with
Guix. Currently only uBlock Origin has been packaged, but adding others
should be technically straight forward. Practically it turns out
somewhat difficult because many extensions rely on the node.js ecosystem.
Patch 1/2 adds a search path mechanism to ungoogled-chromium such that
it looks for local extensions in $CHROMIUM_EXTENSION_DIRECTORY instead
of the default "/usr/share/chromium/extensions".
Patch 2/2 adds a generic MAKE-CHROMIUM-EXTENSION procedure that turns
a <package> object containing an uncompressed extension directory into
a signed .crx file visible to Chromium through a crafted JSON file.
There is one problem with the proposed patches: extensions are not
automatically updated. That is, updating the "ublock-origin-chromium"
package will not update the browser profile even after a browser
restart. Worse, uninstalling the extension through Chromium will leave
you no way to install it again even after it has been updated.
Not sure if that should be a blocking issue.
I'm also not sure whether (gnu packages browser-extensions) is a good
home for the helper procedures that create signing key, etc. Thoughts?
To aid testing I have started a build of the patched ungoogled-chromium
on ci.guix.gnu.org[*]. It should be finished by tomorrow(!).
(testers can use "chromium --user-data-dir=/tmp/foo" to avoid messing
with their regular profile)
I'm currently relocating to a new city and won't be able to follow up
on this until next week. In the meantime, feedback very welcome!
[*] on commit eee35fe3b7cb21792b90ecbf5a834b5a3fdb6f04.
Marius Bakke (2):
gnu: ungoogled-chromium: Add search path for installed extensions.
gnu: Add ublock-origin-chromium.
gnu/local.mk | 2 +
gnu/packages/browser-extensions.scm | 274 ++++++++++++++++++
gnu/packages/chromium.scm | 18 +-
.../ungoogled-chromium-search-path.patch | 28 ++
4 files changed, 314 insertions(+), 8 deletions(-)
create mode 100644 gnu/packages/browser-extensions.scm
create mode 100644 gnu/packages/patches/ungoogled-chromium-search-path.patch
--
2.28.0
next reply other threads:[~2020-10-30 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:29 Marius Bakke [this message]
2020-10-30 18:32 ` [bug#44335] [PATCH 1/2] gnu: ungoogled-chromium: Add search path for installed extensions Marius Bakke
2020-10-30 18:32 ` [bug#44335] [PATCH 2/2] gnu: Add ublock-origin-chromium Marius Bakke
2020-11-02 0:22 ` [bug#44335] [PATCH v2 0/3] Install Chromium extensions with Guix! Marius Bakke
2020-11-02 0:22 ` [bug#44335] [PATCH v2 1/3] gnu: ungoogled-chromium: Add search path for installed extensions Marius Bakke
2020-11-02 0:22 ` [bug#44335] [PATCH v2 2/3] Add (gnu build chromium-extension) Marius Bakke
2020-11-02 0:28 ` Marius Bakke
2020-11-02 0:22 ` [bug#44335] [PATCH v2 3/3] gnu: Add ublock-origin-chromium Marius Bakke
2020-11-02 0:55 ` [bug#44335] [PATCH v2 0/3] Install Chromium extensions with Guix! Leo Famulari
2020-11-08 17:38 ` bug#44335: " Marius Bakke
2020-11-08 17:46 ` [bug#44335] " Leo Famulari
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=20201030182925.5151-1-marius@gnu.org \
--to=marius@gnu.org \
--cc=44335@debbugs.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).