From mboxrd@z Thu Jan  1 00:00:00 1970
From: zimoun <zimon.toutoune@gmail.com>
Subject: Re: New build system: copy-build-system
Date: Mon, 27 Jan 2020 16:36:34 +0100
Message-ID: <CAJ3okZ3xB1aagxHroKLfMNTBcHAfx661NzzJhQOvCEKGDGVVqA@mail.gmail.com>
References: <87sgk2dkuv.fsf@ambrevar.xyz>
 <CAJ3okZ2q4XLvk3W9WTEr3_Wwtgh-9K2YEm0eM3jWQLNUBmLxjQ@mail.gmail.com>
 <87pnf5arh1.fsf@ambrevar.xyz>
 <CAJ3okZ0XfiFf5KVV4DWRt-ROBe_GMv=yOSKmJZKmq=UOTNspQw@mail.gmail.com>
 <87k15dapxk.fsf@ambrevar.xyz>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:49595)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <zimon.toutoune@gmail.com>) id 1iw6RT-0005kc-1e
 for guix-devel@gnu.org; Mon, 27 Jan 2020 10:36:48 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <zimon.toutoune@gmail.com>) id 1iw6RR-0001Pf-Va
 for guix-devel@gnu.org; Mon, 27 Jan 2020 10:36:46 -0500
Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]:32924)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <zimon.toutoune@gmail.com>)
 id 1iw6RR-0001PV-Rg
 for guix-devel@gnu.org; Mon, 27 Jan 2020 10:36:45 -0500
Received: by mail-qk1-x736.google.com with SMTP id h23so10028393qkh.0
 for <guix-devel@gnu.org>; Mon, 27 Jan 2020 07:36:45 -0800 (PST)
In-Reply-To: <87k15dapxk.fsf@ambrevar.xyz>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>

On Mon, 27 Jan 2020 at 16:18, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>
> zimoun <zimon.toutoune@gmail.com> writes:

> Actually we could simplify the install plan with something like
>
> --8<---------------cut here---------------start------------->8---
> #:install-plan
> (("source1" "target1")
>  ("source-dir2/" "target-dir2" #:exclude ("foo")))
> --8<---------------cut here---------------end--------------->8---

Yes. For sure. :-)

> Regarding the data fetching, if I understand your point I think it
> should be handled in a separate issue.

Maybe. :-)
It is just the occasion to pop out again the issue.
And why not discuss how to deal with large data set. I mean, if I use
my typical french bad faith in grumpy fashion, then I do not see why
the "small" data set are included in the store and the "large" not.
What does fix the definition of "small" and "large"?


And for example, the 'copy-build-system' could:

 - fetch the data from an archive, such http://data.astrometry.net or
IPFS or Zenodo or <name-it>
 - fetch the resulting <hash> of /gnu/store/<hash>-name-version from susbtitutes

Other said design a build-system to manage large dataset as regular packages.
Yes, it is out of scope of your initial idea. :-)


Cheers,
simon