From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: support for containers
Date: Tue, 29 Jan 2019 22:52:53 +0100 [thread overview]
Message-ID: <CAJ3okZ1dhN4uD2sSEYjSbhHnNwkc9c+_g_X=H+2y6Xn08aZ9eA@mail.gmail.com> (raw)
In-Reply-To: <874l9rpeiq.fsf@elephly.net>
Hi Ricardo,
I follow your explanations, I think.
What it is not clear to me is: how many store do we consider?
1. one managing the package. Everything already here. Nothing to tell more. :-)
2. one about scripts
3. one about data
Or the scripts and the data do they live in the same store? And the
script is just considered as a kind-of derivation for the data.
Hum? it is out of container scope, isn't it?
Well, thank you for the container support. :-)
All the best,
simon
next prev parent reply other threads:[~2019-01-29 23:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 23:03 support for containers Ricardo Wurmus
2019-01-29 9:38 ` Ricardo Wurmus
2019-01-29 10:39 ` zimoun
2019-01-29 11:46 ` Ricardo Wurmus
2019-01-29 14:29 ` zimoun
2019-01-29 17:19 ` Ricardo Wurmus
2019-01-29 21:52 ` zimoun [this message]
2019-01-29 23:16 ` Ricardo Wurmus
2019-01-30 10:17 ` zimoun
2019-01-30 12:46 ` Ricardo Wurmus
2019-01-29 10:22 ` zimoun
2019-01-29 11:44 ` Ricardo Wurmus
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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ1dhN4uD2sSEYjSbhHnNwkc9c+_g_X=H+2y6Xn08aZ9eA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).