From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: New build system: copy-build-system
Date: Mon, 27 Jan 2020 16:36:34 +0100 [thread overview]
Message-ID: <CAJ3okZ3xB1aagxHroKLfMNTBcHAfx661NzzJhQOvCEKGDGVVqA@mail.gmail.com> (raw)
In-Reply-To: <87k15dapxk.fsf@ambrevar.xyz>
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
next prev parent reply other threads:[~2020-01-27 15:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 20:27 New build system: copy-build-system Pierre Neidhardt
2020-01-27 0:45 ` Jesse Gibbons
2020-01-27 4:14 ` Jack Hill
2020-01-27 14:27 ` zimoun
2020-01-27 14:44 ` Pierre Neidhardt
2020-01-27 15:03 ` zimoun
2020-01-27 15:18 ` Pierre Neidhardt
2020-01-27 15:36 ` zimoun [this message]
2020-01-27 15:51 ` Pierre Neidhardt
2020-01-27 16:17 ` zimoun
2020-01-27 18:18 ` Julien Lepiller
2020-01-27 16:45 ` How to deal with very large sources Ricardo Wurmus
2020-01-27 19:03 ` New build system: copy-build-system Ricardo Wurmus
2020-01-28 10:32 ` Ludovic Courtès
2020-01-28 13:39 ` Pierre Neidhardt
2020-01-28 23:04 ` Ludovic Courtès
2020-02-14 12:54 ` Pierre Neidhardt
2020-02-14 13:22 ` Julien Lepiller
2020-02-17 3:46 ` Jesse Gibbons
2020-02-17 7:56 ` Pierre Neidhardt
2020-02-17 16:52 ` Jesse Gibbons
2020-02-17 17:10 ` Pierre Neidhardt
2020-02-19 1:33 ` Alex Griffin
2020-02-19 14:01 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3xB1aagxHroKLfMNTBcHAfx661NzzJhQOvCEKGDGVVqA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.