From debbugs-submit-bounces@debbugs.gnu.org Sat May 02 18:12:17 2015 Received: (at 20255) by debbugs.gnu.org; 2 May 2015 22:12:17 +0000 Received: from localhost ([127.0.0.1]:60027 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Yofdw-0000E4-CI for submit@debbugs.gnu.org; Sat, 02 May 2015 18:12:16 -0400 Received: from fencepost.gnu.org ([208.118.235.10]:48793 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Yofdu-0000Dw-Lo for 20255@debbugs.gnu.org; Sat, 02 May 2015 18:12:15 -0400 Received: from reverse-83.fdn.fr ([80.67.176.83]:40890 helo=pluto) by fencepost.gnu.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1Yofdt-0006Us-OF; Sat, 02 May 2015 18:12:14 -0400 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) To: =?utf-8?B?5a6L5paH5q2m?= Subject: Re: bug#20255: 'search-paths' should respect both user and system profile. References: <877ftschjt.fsf@gmail.com> <87fv8fip01.fsf@gnu.org> <87d23j1bxk.fsf@gmail.com> <871tjyfnl8.fsf@gnu.org> <876199q4z1.fsf@gmail.com> Date: Sun, 03 May 2015 00:12:11 +0200 In-Reply-To: <876199q4z1.fsf@gmail.com> (=?utf-8?B?IuWui+aWh+atpiIncw==?= message of "Mon, 06 Apr 2015 12:02:26 +0800") Message-ID: <87ioca4ojo.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 20255 Cc: 20255@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.0 (-----) =E5=AE=8B=E6=96=87=E6=AD=A6 skribis: >> [...] >>> >>> The idea to generate profile from search-paths is not new, >>> I heard it from you IIRC. >>> I think it's the time to do it. >> >> Agreed, the plan makes sense and I think we have all the bits. >> >> A related question is whether to encode search path environment >> variables into the manifest (currently they are =E2=80=9Cguessed=E2=80= =9D by looking at >> same-named packages; see (guix build package).) I think that would >> probably simplify things and make it easier to share this environment >> variable code. >> >> Thoughts? > I see, currently search-paths depends on the packages recipes. If we > update the related scheme code, then search-paths got updated, even we > didn't touch packages in profile at all. It's a little confusing. > So I think we should encode the search-paths for each package in > manifest. Done in dedb17a. That will make it easier to generate environment variable settings. Ludo=E2=80=99.