From: "Feng Shu" <tumashu@163.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26532@debbugs.gnu.org
Subject: bug#26532: Re: bug#26532: [PATCH] gnu: update you-get version
Date: Tue, 18 Apr 2017 06:07:15 +0800 [thread overview]
Message-ID: <87efwq7koc.fsf@163.com> (raw)
In-Reply-To: <87inm3kqvh.fsf@fastmail.com> (Marius Bakke's message of "Mon, 17 Apr 2017 17:14:58 +0200")
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Marius Bakke <mbakke@fastmail.com> writes:
> 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.
344.5MiB ...
you are right, tarball seem to be a better approach.
>
> 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 :)
>
This is a very useful tip, thanks!
the below is updated patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-update-you-get-version.patch --]
[-- Type: text/x-patch, Size: 1153 bytes --]
From 77df519f20b5304ec0e838ad519aef26ab18115c Mon Sep 17 00:00:00 2001
From: Feng Shu <tumashu@163.com>
Date: Tue, 18 Apr 2017 06:04:12 +0800
Subject: [PATCH] gnu: update you-get version
* gnu/packages/video.scm (you-get): Update you-get version
---
gnu/packages/video.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/video.scm b/gnu/packages/video.scm
index e1c6a989f..dcac350d0 100644
--- a/gnu/packages/video.scm
+++ b/gnu/packages/video.scm
@@ -1105,7 +1105,7 @@ other site that youtube-dl supports.")
(define-public you-get
(package
(name "you-get")
- (version "0.4.652")
+ (version "0.4.715")
(source (origin
(method url-fetch)
(uri (string-append
@@ -1113,7 +1113,7 @@ other site that youtube-dl supports.")
version "/you-get-" version ".tar.gz"))
(sha256
(base32
- "0brkz98lycx8mmxjwmn7jlhqfdbvl0hy070n7skwr1k75kh99q30"))))
+ "043122hfh56fbbszp1kwd1f65asgyn60j1ijday93hf2dkhvbrnh"))))
(build-system python-build-system)
(arguments
;; no tests
--
2.12.2
[-- Attachment #3: Type: text/plain, Size: 7 bytes --]
--
next prev parent reply other threads:[~2017-04-17 22:08 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
2017-04-17 22:07 ` Feng Shu [this message]
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=87efwq7koc.fsf@163.com \
--to=tumashu@163.com \
--cc=26532@debbugs.gnu.org \
--cc=mbakke@fastmail.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).