From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Adding a note to 3.6 Invoking guix pull Date: Sun, 4 Nov 2018 10:47:39 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------CE81D58E9CA79E9F9198003A" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46280) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJF0a-0005kg-Qb for guix-devel@gnu.org; Sun, 04 Nov 2018 04:47:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJF0X-0007R8-JZ for guix-devel@gnu.org; Sun, 04 Nov 2018 04:47:52 -0500 Received: from mx1.riseup.net ([198.252.153.129]:55362) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gJF0V-0007O2-HZ for guix-devel@gnu.org; Sun, 04 Nov 2018 04:47:48 -0500 Received: from piha.riseup.net (piha-pn.riseup.net [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 8FF121A046E for ; Sun, 4 Nov 2018 01:47:45 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by piha.riseup.net with ESMTPSA id 8FCDB63586 for ; Sun, 4 Nov 2018 01:47:44 -0800 (PST) Content-Language: en-US List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org This is a multi-part message in MIME format. --------------CE81D58E9CA79E9F9198003A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi The more I use guix pull the less I feel like updating guix this way. I saw a long time ago a post from Ricardo about updating guix directly from the source tree. I think this way of updating guix should be written clearly in the manual and perhaps be noted in 3.6 Invoking guix pull I think we need a whole new section between 3. and 4. titled "Upgrading Guix" with 2 subsections: 1. Invoking guix pull 2. Via guix source tree What do you think? -- Cheers Swedebugia --------------CE81D58E9CA79E9F9198003A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Hi

The more I use guix pull the less I feel like updating guix this way.

I saw a long time ago a post from Ricardo about updating guix directly from the source tree.

I think this way of updating guix should be written clearly in the manual and perhaps be noted in 3.6 Invoking guix pull

I think we need a whole new section between 3. and 4. titled "Upgrading Guix" with 2 subsections:

  1. Invoking guix pull
  2. Via guix source tree

What do you think?

-- 
Cheers
Swedebugia
--------------CE81D58E9CA79E9F9198003A--