unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Roel Janssen <roel@gnu.org>
Cc: gwl-devel@gnu.org
Subject: Moving GWL modules
Date: Wed, 19 Dec 2018 22:22:43 +0100	[thread overview]
Message-ID: <87zht1rz30.fsf@elephly.net> (raw)

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 …)”.

What do you think?

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?

Thanks!

--
Ricardo

             reply	other threads:[~2018-12-19 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 21:22 Ricardo Wurmus [this message]
2018-12-19 22:07 ` Moving GWL modules Roel Janssen
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=87zht1rz30.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. 
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).