On Mon, 27 Jan 2020 at 16:18, Pierre Neidhardt <m...@ambrevar.xyz> wrote:
>
> zimoun <zimon.touto...@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
