unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: The tricky case of "--localstatedir=/var"
Date: Wed, 17 Feb 2016 19:23:06 +0100	[thread overview]
Message-ID: <20160217182306.GA31115@solar> (raw)
In-Reply-To: <CAEKzfH=qb2Qek0Gz-nvE_ppTj89Ze_aPMsp5u2M2yo-E0o639A@mail.gmail.com>

On Wed, Feb 17, 2016 at 05:50:31PM +0000, Chris Marusich wrote:
> I understand why it's
> nice to have the Guix package so that you can easily work with its
> dependencies, but isn't "guix pull" the recommended way to keep your Guix
> installation up to date?

As far as I know, the only ways of getting the latest and greatest of Guix
is to use "guix pull" or a git checkout. The guix package inside guix
corresponds to a more or less random git commit after the last release,
and is only updated occasionally. In particular, the current version does
not contain all the recent security fixes. So I can only recommend against
using "guix package -i guix".

Andreas

  parent reply	other threads:[~2016-02-17 18:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 13:57 The tricky case of "--localstatedir=/var" Jookia
2016-02-16 14:29 ` Ricardo Wurmus
2016-02-16 14:52   ` Jookia
2016-02-16 16:41   ` Andreas Enge
2016-02-16 17:12     ` Jookia
2016-02-16 17:16       ` Andreas Enge
2016-02-16 16:04 ` Tobias Geerinckx-Rice
2016-02-16 16:08   ` Tobias Geerinckx-Rice
2016-02-16 19:11 ` Christopher Allan Webber
2016-02-16 19:59 ` Danny Milosavljevic
2016-02-16 22:42   ` Mark H Weaver
2016-02-17  9:29     ` Ricardo Wurmus
2016-02-17  8:06 ` Chris Marusich
2016-02-17  8:38   ` Jookia
2016-02-17  9:15     ` Chris Marusich
2016-02-17 10:08       ` Jookia
2016-02-17 17:50         ` Chris Marusich
2016-02-17 18:00           ` Jookia
2016-02-17 18:23           ` Andreas Enge [this message]
2016-03-17 22:11 ` Ludovic Courtès
2016-03-17 22:19   ` Mathieu Lirzin
2016-03-18  1:12   ` Jookia
2016-03-18 18:45     ` Ludovic Courtès
2016-03-19  3:27       ` Jookia
2016-03-19 14:11   ` 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=20160217182306.GA31115@solar \
    --to=andreas@enge.fr \
    --cc=cmmarusich@gmail.com \
    --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).