From: Jelle Licht <jlicht@fsfe.org>
To: guixuser <guixuser@protonmail.com>, "me@tobias.gr" <me@tobias.gr>
Cc: "guix-devel\\@gnu.org" <guix-devel@gnu.org>,
"help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: IceWeasel-UXP and IceDove-UXP
Date: Sat, 20 Jul 2019 00:58:31 +0200 [thread overview]
Message-ID: <87lfwttyw8.fsf@jlicht.xyz> (raw)
In-Reply-To: <CIipS7bDEJMZClKu1Km6EdTIEZKbhJHh0BAQsfxTPzsPAz8OgoRVZmwBVywV8gN0w7p_wRCLKp5FO57FbDkkogGf8iwpS4v2icOTcGIKVLw=@protonmail.com>
Hey guixuser,
guixuser <guixuser@protonmail.com> writes:
> [use this thread]
>
> Budget? Are you serious? Any distro has to focus on their basic things like email and browser for new user; at least if project wants to grow and accommodate new users.
For at least your browsing needs, I know of two options.
Guix currently has IceCat, which is as close to FireFox as you can get
while still being a FSDG-distro. I assume that if one is used to
IceWeasel, using IceCat should feel very familiar. The only iffy part is
working with extensions that are not yet available in the IceCat
upstream list of supported web extensions.
There is also an `ungoogled-chromium' package, but be aware that this
can take quite some time to build on your local machine if no binary
substitutes are available.
Getting used to the guix way of doing things can take some time and
effort, but it is IMHO definitely worth the investment. Guix empowers
users to exert control over their computing in a way that few other
software does.
If you run into any unclear steps in the documentation or are missing
packages, there are usually people available on the mailing list or on
#guix on the Freenode IRC network to help you figure out how to get
something working.
next prev parent reply other threads:[~2019-07-19 22:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 20:13 IceWeasel-UXP and IceDove-UXP guixuser
2019-07-19 21:10 ` Ricardo Wurmus
2019-07-19 21:16 ` guixuser
2019-07-19 21:50 ` Ricardo Wurmus
2019-07-19 21:56 ` guixuser
2019-07-20 16:38 ` Jesse Gibbons
2019-07-20 16:48 ` guixuser
2019-07-21 8:07 ` N
2019-07-23 5:08 ` Jesse Gibbons
2019-07-23 7:07 ` N
2019-07-20 17:01 ` Raghav Gururajan
2019-07-31 23:39 ` Jesse Gibbons
2019-07-19 21:53 ` guixuser
2019-07-19 22:58 ` Jelle Licht [this message]
2019-07-19 23:57 ` Tobias Geerinckx-Rice
2019-07-20 0:03 ` guixuser
2019-07-21 0:43 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2019-07-19 13:29 Iceweasel-UXP and Icedove-UXP Guix User
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=87lfwttyw8.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=guix-devel@gnu.org \
--cc=guixuser@protonmail.com \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).