From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Warning on using 'guix pull'
Date: Thu, 9 Feb 2017 13:32:53 +0000 [thread overview]
Message-ID: <20170209133253.GA23454@mail.thebird.nl> (raw)
@FOSDEM we concluded that 'guix pull' does not necessarily work
that wel. I added to my guix-notes the following:
+Health warning: at this point 'guix pull' is considered a liability for two reasons
+
+1. You don't know what you get even if it is considered 'latest'
+2. Guix pull runs over http and is not considered safe
+
--
next reply other threads:[~2017-02-09 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:32 Pjotr Prins [this message]
2017-02-09 16:00 ` Warning on using 'guix pull' 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=20170209133253.GA23454@mail.thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@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).