From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: Blog team
Date: Tue, 24 Apr 2018 17:05:45 +0200 [thread overview]
Message-ID: <87tvs0skza.fsf@elephly.net> (raw)
In-Reply-To: <87fu3kyfx7.fsf@gmail.com>
Hi Pierre,
> I recently had a fair discussion over Guix vs. NixOS vs. the world:
>
> https://www.reddit.com/r/emacs/comments/8a94rt/helm_system_packages_update_guix_xbps_void_linux/
Here’s another one for reference in response to the question “What are
the advantages of guix vs nix?”:
https://news.ycombinator.com/item?id=16491797
> One of the hottest topic that I'm tackling at the moment is the
> management of non-opensource installs. […]
> Not completely sure that would fit a Guix blog entry though :p
Yeah, I think this should not be published on the official project blog,
as non-free software really is out of scope for our project.
--
Ricardo
next prev parent reply other threads:[~2018-04-24 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 8:25 Blog team Ludovic Courtès
2018-04-24 11:58 ` Pierre Neidhardt
2018-04-24 15:05 ` Ricardo Wurmus [this message]
2018-04-24 15:57 ` Pierre Neidhardt
2018-04-25 12:41 ` Ludovic Courtès
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=87tvs0skza.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=ambrevar@gmail.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@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.
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).