[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0.
From: |
Arun Isaac |
Subject: |
bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0. |
Date: |
Mon, 29 May 2017 03:48:36 +0530 |
>> 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?
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Alex Griffin, 2017/05/27
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Arun Isaac, 2017/05/28
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Leo Famulari, 2017/05/28
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Arun Isaac, 2017/05/29
- Message not available
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Leo Famulari, 2017/05/29
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Arun Isaac, 2017/05/30
- Message not available
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Marius Bakke, 2017/05/30
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Arun Isaac, 2017/05/30