From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Python 3 native-search-paths Date: Sun, 01 Sep 2013 15:31:45 +0200 Message-ID: <877gf0r7lq.fsf@gnu.org> References: <20130831154014.GA5736@debian> <87wqn1sv20.fsf@gnu.org> <20130831164305.GA9597@debian> <8761ulspjp.fsf@gnu.org> <20130901071112.GA7907@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VG7pm-00062y-VV for guix-devel@gnu.org; Sun, 01 Sep 2013 09:37:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VG7pg-0002Eo-OR for guix-devel@gnu.org; Sun, 01 Sep 2013 09:36:54 -0400 Received: from hera.aquilenet.fr ([141.255.128.1]:58759) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VG7pg-0002Ei-IP for guix-devel@gnu.org; Sun, 01 Sep 2013 09:36:48 -0400 In-Reply-To: <20130901071112.GA7907@debian> (Andreas Enge's message of "Sun, 1 Sep 2013 09:11:12 +0200") List-Id: 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Andreas Enge Cc: guix-devel@gnu.org Andreas Enge skribis: > On Sat, Aug 31, 2013 at 08:06:34PM +0200, Ludovic Court=C3=A8s wrote: >> It has no effect in the build of Python itself; its effect is only when >> building Python code that uses Python and one or more Python libs. > > I still think something is wrong here and that this variable should be > included into the computation of the hash. When I now recompile a > package depending on python, it gets the same hash, but it is different. > > Or more easily: The python package with the new native-search-paths behav= es > differently from the previous one, so it should have a different hash. The hash is the hash of all the inputs to the build process, recursively. If a single bit changes somewhere, the hash changes. But here, search path specifications do not affect the build process of packages that carry them in any way (an improvement over Nix where everything is an environment variable, and thus an input to the hash, even if it is not meant to influence the build process.) When =E2=80=98native-search-paths=E2=80=99 changes in python3, it=E2=80=99s= not python3 that behaves differently: it=E2=80=99s the build process of packages using it th= at does. Hope this clarify things. Thanks, Ludo=E2=80=99.