From: Arun Isaac <arunisaac@systemreboot.net>
To: Leo Famulari <leo@famulari.name>
Cc: 27110@debbugs.gnu.org, Alex Griffin <a@ajgrf.com>
Subject: bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0.
Date: Mon, 29 May 2017 03:48:36 +0530 [thread overview]
Message-ID: <0d20aff7.ADsAAhu0CjwAAAAAAAAAAAPFk78AAAACwQwAAAAAAAW9WABZK0zP@mailjet.com> (raw)
In-Reply-To: <20170528183753.GB15883@jasmine>
>> Could you switch to upstream's github release tarball instead?
>> https://github.com/asciinema/asciinema/archive/v1.4.0.tar.gz
>>
>> LGTM, otherwise!
>
> Is there a reason to prefer one over the other?
>
> I ask because, typically, these unammed GitHub tarballs are not actual
> releases prepared by the maintainers, but just a snapshot of the Git
> repo, created automatically by GitHub for each tag. PyPi tends to
> contain the "real" release in cases like this.
I thought it is better to depend directly on the upstream source
(github, in this case) than on an intermediary (pypi) who has also
packaged the software. If we use pypi, Guix becomes some kind of second
order package repository that depends on pypi, the primary package
repository. WDYT?
next prev parent reply other threads:[~2017-05-28 22:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 1:16 bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0 Alex Griffin
2017-05-28 17:00 ` Arun Isaac
2017-05-28 18:37 ` Leo Famulari
2017-05-28 22:18 ` Arun Isaac [this message]
[not found] ` <2dff1be8.ADsAAhu0Cj4AAAAAAAAAAAO8ccgAAAACwQwAAAAAAAW9WABZK0zP@mailjet.com>
2017-05-28 22:33 ` Leo Famulari
2017-05-28 23:01 ` Marius Bakke
2017-05-29 5:46 ` Arun Isaac
2017-05-29 17:26 ` Arun Isaac
2017-05-29 19:23 ` Arun Isaac
[not found] ` <a9d8e951.AEAAKtByx2QAAAAAAAAAAAO8ccgAAAACwQwAAAAAAAW9WABZLHUl@mailjet.com>
2017-05-29 20:42 ` Leo Famulari
2017-05-30 8:20 ` Arun Isaac
[not found] ` <be173c52.AEMAK1ybgp8AAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZLStT@mailjet.com>
2017-05-30 15:10 ` Marius Bakke
2017-05-30 16:06 ` Arun Isaac
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=0d20aff7.ADsAAhu0CjwAAAAAAAAAAAPFk78AAAACwQwAAAAAAAW9WABZK0zP@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27110@debbugs.gnu.org \
--cc=a@ajgrf.com \
--cc=leo@famulari.name \
/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).