From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: Extending 'guix download'
Date: Mon, 02 Feb 2015 23:00:39 +0100 [thread overview]
Message-ID: <871tm8t1mg.fsf@gnu.org> (raw)
In-Reply-To: <87pp9tjrr7.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Sun, 01 Feb 2015 15:34:04 -0500")
David Thompson <dthompson2@worcester.edu> skribis:
> I'm looking for thoughts about what the CLI should look like for an
> improved 'guix download' that is capable of downloading git repos, svn
> repos, etc. in addition to files over HTTP.
(It handles any scheme supported by ‘url-fetch’, which includes
mirror:// etc.)
> There could be to be additional context-sensitive switches to specify
> details beyond a URL. For example, git repos need a commit SHA.
>
> guix download --method=git --commit=74217b9 git@gitorious.org/foo/foo.git
>
> Or perhaps more flags aren't needed and we can use a specific order of
> arguments:
>
> guix download --method=git git@gitorious.org/foo/foo.git 74217b9
>
> Or we could create subcommands for each download method:
>
> guix download git git@gitorious.org/foo/foo.git 74217b9
That would be useful. Option #3 is too verbose IMO. I have a slight
preference for #2.
The question is more whether the implementation could automatically map
command-line arguments to objects (‘git-reference’, ‘svn-reference’,
etc.), or if we’d rather go for something custom.
The former might be nice but might result in a clumsy CLI; the latter is
less elegant but might allow for a nicer CLI.
WDYT?
Ludo’.
prev parent reply other threads:[~2015-02-02 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 20:34 Extending 'guix download' David Thompson
2015-02-02 22:00 ` Ludovic Courtès [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=871tm8t1mg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@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.