From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kost Subject: Re: [PATCH] build: file-systems: Allow for bind mounting regular files. Date: Fri, 07 Aug 2015 10:06:15 +0300 Message-ID: <87h9obshlk.fsf@gmail.com> References: <87a8uarf6g.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> <87bnepriup.fsf@gmail.com> <87si804jzt.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46215) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZNbjU-0005KS-0b for guix-devel@gnu.org; Fri, 07 Aug 2015 03:06:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZNbjQ-0005An-Ro for guix-devel@gnu.org; Fri, 07 Aug 2015 03:06:23 -0400 Received: from mail-la0-x235.google.com ([2a00:1450:4010:c03::235]:33367) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZNbjQ-0005Ac-JK for guix-devel@gnu.org; Fri, 07 Aug 2015 03:06:20 -0400 Received: by labjt7 with SMTP id jt7so44900359lab.0 for ; Fri, 07 Aug 2015 00:06:18 -0700 (PDT) In-Reply-To: (David Thompson's message of "Thu, 6 Aug 2015 08:22:59 -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: "Thompson, David" Cc: guix-devel Thompson, David (2015-08-06 15:22 +0300) wrote: > On Mon, Aug 3, 2015 at 8:47 AM, Alex Kost wrote: >> Thompson, David (2015-08-02 15:51 +0300) wrote: >> >>> Ah, of course, I forgot about something: This patch triggers a >>> rebuild of *everything* now! I guess it should be applied to >>> core-updates. Or, the first patch I submitted can be applied to >>> master, and then a patch that moves 'regular-file?' to (guix build >>> utils) can be applied to core-updates later. >>> >>> Thoughts? >> >> In my opinion it is redundant to use another commit here, so I would >> apply this patch to core-updates (taking into account Andreas' note). >> But I don't really know how such situations are handled. Mark should >> know better. > > The reason I want two commits is strategic. This first patch can go > into master *now*, without breaking anything or causing a full > rebuild. Moving that procedure into (guix build utils) is nice, but > not strictly necessary. I am trying to get basic container support in > shape and into master. Waiting on a core-updates cycle would just > stall the process. Ah, OK, I don't mind then. -- Alex