From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia@riseup.net Subject: bug#33758: No longer possible to run ./pre-inst-env guix without compiling first Date: Mon, 17 Dec 2018 01:23:47 -0800 Message-ID: <1b022b144a36e5f9c674cac616ac119a@riseup.net> References: <0ed7e834dd4cfdaef62b5dbe334b8d72@riseup.net> <87y38rvzja.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46445) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gYp8B-000712-Aq for bug-guix@gnu.org; Mon, 17 Dec 2018 04:24:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gYp86-00041j-A6 for bug-guix@gnu.org; Mon, 17 Dec 2018 04:24:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:46570) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gYp86-00041X-4l for bug-guix@gnu.org; Mon, 17 Dec 2018 04:24:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gYp85-0003tM-Vl for bug-guix@gnu.org; Mon, 17 Dec 2018 04:24:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87y38rvzja.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 33758@debbugs.gnu.org On 2018-12-15 11:45, Ricardo Wurmus wrote: > swedebugia@riseup.net writes: > >> Is this a bug? > > I’m inclined to say that it is not. > What is the use case here? Well my use case is browsing commits and settling on one with good "weather". Its not that important to me actually because close to master (a few days back there are often >93% substitutes availiable. We could definitely improve the "running from git" section with some kind of best-practice. e.g. keep close to master run clean-go if you get weird guile errors during make (especially after merging of core-updates) etc. Would that be accepted? -- Cheers Swedebugia