From: Roel Janssen <roel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Moving GWL modules
Date: Wed, 19 Dec 2018 23:07:11 +0100 [thread overview]
Message-ID: <95b6b274-d1bc-b0b2-543d-3ceb91e85d1e@gnu.org> (raw)
In-Reply-To: <87zht1rz30.fsf@elephly.net>
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)
Could we keep (guix processes) and (guix workflows) for backwards
compatibility? At least for now, so we don't break existing workflows
right away.
> 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)).
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2018-12-19 22:07 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 [this message]
2018-12-19 22:49 ` 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=95b6b274-d1bc-b0b2-543d-3ceb91e85d1e@gnu.org \
--to=roel@gnu.org \
--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).