[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: |
Tue, 30 May 2017 13:50:27 +0530 |
> In my experience, it seems like the PyPi tarballs are what the upstream
> projects want distributors to use.
>
> So, I usually use what's on PyPi, but it depends.
By preferring pypi, I worry that we promote a kind of centralization. In
my romanticized vision for the future, I see every one self-hosting
their own servers, serving code for their projects, and guix pulling and
building from all of them. This is why I find excessive dependence on
pypi disturbing. We are also creating a single point of failure/attack
at pypi. Granted that everyone using github to host their projects is
not much better, still...
- 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/28
- Message not available
- 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., Marius Bakke, 2017/05/28
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Arun Isaac, 2017/05/29
- bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0., Arun Isaac, 2017/05/29
- 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 <=
- 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