From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCH] Improve shell script headers and pre-inst-env handling Date: Tue, 12 Feb 2013 13:44:58 -0500 Message-ID: <87d2w5xtg5.fsf@tines.lan> References: <87haliz4nt.fsf@tines.lan> <87fw11v83n.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:39212) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5Kqz-0003KL-R9 for bug-guix@gnu.org; Tue, 12 Feb 2013 13:45:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5Kqv-0001MQ-Q4 for bug-guix@gnu.org; Tue, 12 Feb 2013 13:45:17 -0500 In-Reply-To: <87fw11v83n.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 12 Feb 2013 16:56:44 +0100") 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-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: bug-guix@gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Honestly, I wouldn=E2=80=99t worry about the propagation of $GUILE_LOAD_P= ATH & > co. to subprocesses, because we know there=E2=80=99s none anyway. That policy will lead to future where libguile-using programs break in random ways when they happen to be subprocesses of each other. Shouldn't we be setting a better example than that? If we assume that Guile will never be widely used, and encourage usage patterns that will cause things to break if it ever becomes more successful, then we are pretty much guaranteeing a bleak future for Guile. Isn't correctness more important than brevity? What do you think? Mark