From: Marius Bakke <mbakke@fastmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>,
Leo Famulari <leo@famulari.name>
Cc: 27110-done@debbugs.gnu.org, Alex Griffin <a@ajgrf.com>
Subject: bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0.
Date: Tue, 30 May 2017 17:10:47 +0200 [thread overview]
Message-ID: <87shjme5xk.fsf@fastmail.com> (raw)
In-Reply-To: <be173c52.AEMAK1ybgp8AAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZLStT@mailjet.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
Arun Isaac <arunisaac@systemreboot.net> writes:
>> 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...
I don't find Github better at all. One is a centralized source code
hosting platform, the other is a centralized Python package publishing
platform.
In the rare case where the package is hosted elsewhere (e.g. on a
personal/project home page) then we should use that*, but I have no
real preference between github/bitbucket/etc and PyPi other than
PyPi packages often being more "polished".
* Usually**, such pages just link to PyPi.
** See "python-cram" for a counter-example.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-05-30 15:11 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
[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 [this message]
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=87shjme5xk.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=27110-done@debbugs.gnu.org \
--cc=a@ajgrf.com \
--cc=arunisaac@systemreboot.net \
--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).