From: swedebugia@riseup.net
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Gabriel Hondet <gabrielhondet@gmail.com>,
guix-devel <guix-devel@gnu.org>,
Guix-devel <guix-devel-bounces+swedebugia=riseup.net@gnu.org>
Subject: Re: Stating the size of ecosystems in descriptions
Date: Wed, 16 Jan 2019 15:56:04 -0800 [thread overview]
Message-ID: <d58c0ca6ce2df601d9734dbba14f8522@riseup.net> (raw)
In-Reply-To: <877ef4idgz.fsf@elephly.net>
On 2019-01-16 19:55, Ricardo Wurmus wrote:
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>> I’d prefer not to add a feature like this.
>>
>> Why not?
>
> Lots of reasons.
>
> One reason is that pypi isn’t the only source of Python packages. Nor
> is CRAN the only source of R packages. There are also package sources
> that we fetch from other locations because of problems with whatever has
> been published on the more popular repositories (e.g. most of the
> rubygems).
>
> I also think it’s not the job of a package manager to tell you how much
> software there is in this world and how much of it can be accessed via
> the package manager. What good are those numbers? What useful
> information do they provide? I don’t think it’s good to clutter the
> list of commands (and the documentation) with features of very limited
> usefulness.
>
> I don’t like the ways it would work: neither do I want to store and
> regularly update lists of remote packages nor do I want to have my
> package manager call out to remote web servers. What about packages
> that are not available because they are not free software?
>
> (Finally, I don’t like the use of the word “ecosystem” in the realm of
> software.)
OK. Thanks for stating this Ricardo. Pierre, I'm fine with removing the
sentence with the number altogether.
--
Cheers
Swedebugia
next prev parent reply other threads:[~2019-01-16 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 9:47 Gauche description Pierre Neidhardt
2019-01-16 11:58 ` Stating the size of ecosystems in descriptions (Was: Re: Gauche description) swedebugia
2019-01-16 12:53 ` Pierre Neidhardt
2019-01-16 14:52 ` Gabriel Hondet
2019-01-16 15:42 ` Stating the size of ecosystems in descriptions swedebugia
2019-01-16 17:12 ` Stating the size of ecosystems in descriptions (Was: Re: Gauche description) Ricardo Wurmus
2019-01-16 17:27 ` Pierre Neidhardt
2019-01-16 19:55 ` Ricardo Wurmus
2019-01-16 23:56 ` swedebugia [this message]
2019-01-17 7:33 ` Stating the size of ecosystems in descriptions Pierre Neidhardt
2019-01-16 13:03 ` Stating the size of ecosystems in descriptions (Was: Re: Gauche description) Ricardo Wurmus
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=d58c0ca6ce2df601d9734dbba14f8522@riseup.net \
--to=swedebugia@riseup.net \
--cc=gabrielhondet@gmail.com \
--cc=guix-devel-bounces+swedebugia=riseup.net@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).