From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Problems with handicapped 'bash' from glibc package Date: Sun, 23 Mar 2014 21:27:33 +0100 Message-ID: <87siq8r77u.fsf@gnu.org> References: <871tz8oldk.fsf@netris.org> <874n2oubuq.fsf@gnu.org> <8761n4mzvu.fsf@yeeloong.lan> 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]:59581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRozc-00037R-1P for guix-devel@gnu.org; Sun, 23 Mar 2014 16:27:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WRozX-0007wa-AN for guix-devel@gnu.org; Sun, 23 Mar 2014 16:27:39 -0400 Received: from hera.aquilenet.fr ([2a01:474::1]:45509) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRozX-0007wV-3V for guix-devel@gnu.org; Sun, 23 Mar 2014 16:27:35 -0400 In-Reply-To: <8761n4mzvu.fsf@yeeloong.lan> (Mark H. Weaver's message of "Sun, 23 Mar 2014 16:19:33 -0400") 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Mark H Weaver Cc: guix-devel@gnu.org Mark H Weaver skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Mark H Weaver skribis: >> >>> The 'bash' in the glibc package is handicapped in at least two ways: >>> >>> * It can't set the locale, because it looks for locales in >>> /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-glibc-intermediate-2.18-l= ocales >>> >>> * It can't look up anything from NSS, such as passwd data, because it >>> tries to load the modules from >>> /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-glibc-intermediate-2.18 >>> >>> There are two problems that need to be addressed, I think: >>> >>> * Users could easily end up with this handicapped 'bash' as their >>> primary bash, if they installed (or upgraded?) 'glibc' since the last >>> time I installed 'bash'. This happened to me, for example. >> >> I realized that this particular problem is easily solved by moving >> glibc=E2=80=99s bash away from $bindir, for instance to $libexecdir. >> >> I=E2=80=99m trying it out locally, and plan to commit to core-updates if >> everything works as expected (hopefully as the last core-updates >> change.) >> >> Thoughts? > > Hmm. We need a more intelligent union.scm anyway, Agreed, but that=E2=80=99s a separate issue. Having it in $bindir also means that patch-shebangs can pick it up, which is usually not what we want. So I think it really makes sense to move it out of sight. > and that would solve this problem and many others. Therefore, I'd be > inclined to avoid making this change, and instead work on union.scm. > I want to optimize it anyway, since it takes over 5 minutes to build > my profile, which is a bit painful. Oh, this much? I have 140 packages in my profile and it takes less than 30s to build it; that=E2=80=99s an SSD though, so that probably makes a big difference. > I confess that I'm biased, because it would mean throwing away most of > the core-updates build outputs my YeeLoong 8101B has produced over the > last four days, and starting again from scratch :-( Yeah, I understand the frustration. However, I really view core-updates as the place where we can make this kind of change without having to pay much attention to build time (though I reckon this one occurs close to the intended merge date.) Ludo=E2=80=99.