From: Ricardo Wurmus <rekado@elephly.net>
To: Roel Janssen <roel@gnu.org>
Cc: gwl-devel@gnu.org
Subject: Re: Moving GWL modules
Date: Wed, 19 Dec 2018 23:49:03 +0100 [thread overview]
Message-ID: <87tvj9rv34.fsf@elephly.net> (raw)
In-Reply-To: <95b6b274-d1bc-b0b2-543d-3ceb91e85d1e@gnu.org>
Hi Roel,
> On 19-12-18 22:22, Ricardo Wurmus wrote:
>> Hi Roel,
>>
>> I’m interested in moving the GWL modules to their own namespace to avoid
>> potential clashes with future versions of Guix. Currently, GWL modules
>> share the “(guix …)” and “(gnu …)” namespaces.
>>
>> I think it would be clearer to move all but the scripts (which extend
>> Guix) to “(gwl …)”.
>
> I like this change. So the new modules would be:
> (gwl processes) and (gwl workflows)
Correct.
> Could we keep (guix processes) and (guix workflows) for backwards
> compatibility? At least for now, so we don't break existing workflows
> right away.
Yes, we can keep them for now; or we could let them re-export all of the
new modules’ symbols for compatibility.
>> On a related note: I can never remember if a procedure is defined in
>> “(gnu workflows)” or “(guix workflows)”. Do you have a mnemonic? Is
>> this separation necessary or would it be fine to rearrange things?
>
> It's fine to rearrange things. I mimic'd the modules for Guix's
> packages ((guix packages) and (gnu packages)).
That’s what I thought :)
Thanks for the quick response!
--
Ricardo
prev parent reply other threads:[~2018-12-19 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 21:22 Moving GWL modules Ricardo Wurmus
2018-12-19 22:07 ` Roel Janssen
2018-12-19 22:49 ` Ricardo Wurmus [this message]
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=87tvj9rv34.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=roel@gnu.org \
/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.