From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: GuixSD installation: binary vs source packages
Date: Sat, 25 Feb 2017 10:52:36 -0500
Message-ID: <20170225155236.GA3227@jasmine>
References: <RKjslCs1toc6oiS8cLM8vVhDde45JQ2SLy6p2UrRZkWZQOqyELrSjri_PXeFlYa4HSJfz38Jri0uZHum8cSBDFQzqu__dxcQcV-a9MlucEY=@protonmail.ch>
	<8660jzav0c.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58427)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1cheeK-0003Nv-If
	for help-guix@gnu.org; Sat, 25 Feb 2017 10:52:45 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1cheeF-0004qk-Lh
	for help-guix@gnu.org; Sat, 25 Feb 2017 10:52:44 -0500
Received: from out4-smtp.messagingengine.com ([66.111.4.28]:46223)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <leo@famulari.name>) id 1cheeF-0004qe-GN
	for help-guix@gnu.org; Sat, 25 Feb 2017 10:52:39 -0500
Content-Disposition: inline
In-Reply-To: <8660jzav0c.fsf@gmail.com>
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix/>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: myglc2 <myglc2@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>, Alex Vestgaard <birkeroed@protonmail.ch>

On Fri, Feb 24, 2017 at 09:01:39PM -0500, myglc2 wrote:
> In my practical experience of running a GuixSD headless server for the
> last 12 months, if you use 'guix pull', which is effectively a rolling
> release, there is no way to tell.

The default action of `guix pull` is like a rolling release, but you can
also use it to deploy any version or Git commit of Guix, using `guix
pull --url=...`:

https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8a9cffb202414b20081910115ba76402924bdcdd

You still can't be sure that we will have binary substitutes for every
package. I just wanted to point out this little-known feature of `guix
pull`, which gives Guix users some more flexibility without requiring
them to maintain a Guix development environment.