From: Marius Bakke <mbakke@fastmail.com>
To: Feng Shu <tumashu@163.com>
Cc: 26532@debbugs.gnu.org
Subject: bug#26532: Re: bug#26532: [PATCH] gnu: update you-get version
Date: Mon, 17 Apr 2017 17:14:58 +0200 [thread overview]
Message-ID: <87inm3kqvh.fsf@fastmail.com> (raw)
In-Reply-To: <87inm3mjtg.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
Feng Shu <tumashu@163.com> writes:
> tumashu <tumashu@163.com> writes:
>
> This is the updated patch, I use git-fetch instead of url-fetch for I
> want to package git-snapshot if need.
What is the rationale for packaging the git version in anticipation of
needing it later? In this case the latest release is also the latest
commit, so I don't see any compelling reason for switching to git-fetch
at this moment.
Git snapshots use more bandwidth than regular downloads (mostly due to
Guix' lack of shallow clones), and also more disk space since they
create a source derivation. They also introduce a dependency on git
which ticks in at 344.5MiB.
Note that you can also build a package from a local source code copy
with `guix build --with-source=/path/to/git/checkout you-get` in case of
emergency :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-04-17 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 10:33 bug#26532: [PATCH] gnu: update you-get version Feng Shu
2017-04-16 19:12 ` Marius Bakke
2017-04-17 2:27 ` bug#26532: " tumashu
2017-04-17 10:04 ` Feng Shu
2017-04-17 15:14 ` Marius Bakke [this message]
2017-04-17 22:07 ` Feng Shu
2017-04-17 22:33 ` Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inm3kqvh.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=26532@debbugs.gnu.org \
--cc=tumashu@163.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).