From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Do we actually need a “packages” field?
Date: Sun, 2 Feb 2020 13:06:24 +0100 [thread overview]
Message-ID: <CAJ3okZ3ifrzdoufrX5-YphOh+WNffdWTYE12_xEBhyFOVvMQmA@mail.gmail.com> (raw)
In-Reply-To: <87zhe1s27y.fsf@elephly.net>
Hi Ricardo,
On Sun, 2 Feb 2020 at 11:39, Ricardo Wurmus <rekado@elephly.net> wrote:
> What do you think?
Well, considering Mercurial, does it become?
-8<---------------cut here---------------start------------->8---
process: fetch-data
[...]
#{mercurial}/bin/hg clone {{inputs}} {{outputs}}
--8<---------------cut here---------------end--------------->8---
I am not sure it is more readable.
Moreover the user has to know the path.
Even I am not sure to understand why you want to change, from my
opinion, and based on my user experience, it does not matter where I
have to provide the package name but the issue is to find the name of
the package (and the module even if specification->package and related
help).
Cheers,
simon
next prev parent reply other threads:[~2020-02-02 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 10:38 Do we actually need a “packages” field? Ricardo Wurmus
2020-02-02 12:06 ` zimoun [this message]
2020-02-02 12:39 ` 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=CAJ3okZ3ifrzdoufrX5-YphOh+WNffdWTYE12_xEBhyFOVvMQmA@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).