From: Marius Bakke <marius@gnu.org>
To: reza.housseini@gmail.com, help-guix@gnu.org
Subject: Re: ublock extension for ungoogled-chromium
Date: Thu, 03 Feb 2022 11:07:27 +0100 [thread overview]
Message-ID: <87mtj85km8.fsf@gnu.org> (raw)
In-Reply-To: <CAGZc64HOR1ZPo6KgkNxCjz7c8vZZyihZj+8dAae5BRebLvb=qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
Hi Reza,
Reza Housseini <reza.housseini@gmail.com> skriver:
> Hello Guixers
>
> I installed ungoogled-chromium and ublock-origin-chromium and just assumed
> it will work. But it seems that the extension does not get registered in
> chromium. Does anybody know what I have to do to achieve this?
It should definitively "just work", however there are caveats:
* It relies on the $CHROMIUM_EXTENSION_DIRECTORY variable, which is
automatically configured by Guix when you install both packages; but
you may need to log out and in again for it to take effect.
* If you have a previous ~/.config/chromium directory from the (googled)
Chromium laying around, there may be strange interactions.
You can avoid both caveats by running:
guix shell {ungoogled,ublock-origin}-chromium -- \
chromium --user-data-dir=/tmp/chromium-profile
Does the extension show up then?
> Marius Bakke mentioned in his patch [1] that updating does not work, is
> this the reason why?
Updating has since been fixed. :-)
Thanks,
Marius
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-02-03 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGZc64FkC9ojCPobwQ4Wxhc9mJoFAdNLTMdP5ubauXkCS+XuHg@mail.gmail.com>
2022-02-03 9:36 ` ublock extension for ungoogled-chromium Reza Housseini
2022-02-03 10:07 ` Marius Bakke [this message]
2022-02-03 13:03 ` icecat ublock-origin? (Re: ublock extension for ungoogled-chromium) Remco
2022-02-04 9:52 ` ublock extension for ungoogled-chromium Reza Housseini
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=87mtj85km8.fsf@gnu.org \
--to=marius@gnu.org \
--cc=help-guix@gnu.org \
--cc=reza.housseini@gmail.com \
/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.
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).