From: swedebugia@riseup.net
To: Gabriel Hondet <gabrielhondet@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Stating the size of ecosystems in descriptions
Date: Wed, 16 Jan 2019 07:42:01 -0800 [thread overview]
Message-ID: <e39a3ff4ff68acb98ec95277b361ee43@riseup.net> (raw)
In-Reply-To: <87pnswvem1.fsf@gmail.com>
On 2019-01-16 14:52, Gabriel Hondet wrote:
> Hello everyone,
>
> On Wed 16 Jan 2019 at 13:53 Pierre Neidhardt wrote:
>
>> Whichever number we provide will go out of date at some point.
>> It's extra maintenance, and if we only put a rough number (e.g. 100k+) then it's
>> not really meaningful in my opinion.
>
> While I agree with this statement, I also think that Swedebugia's idea of
> comparing the number of Guix-ported packages of an ecosystem with the
> total number of packages in this ecosystem is interesting.
>
> Couldn't something like
>
> #+begin_src sh
> guix ecosystem pypi
> #+end_src
>
> which would retrieve the number of packages on pypi, compute the number
> of pypi packages defined for Guix and output some statistics be done?
+1
This is way better than including it in the definitions, however we
would probably have to parse the websites to get the numbers we need.
--
Cheers
Swedebugia
next prev parent reply other threads:[~2019-01-16 15:42 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 ` swedebugia [this message]
2019-01-16 17:12 ` Ricardo Wurmus
2019-01-16 17:27 ` Pierre Neidhardt
2019-01-16 19:55 ` Ricardo Wurmus
2019-01-16 23:56 ` Stating the size of ecosystems in descriptions swedebugia
2019-01-17 7:33 ` 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=e39a3ff4ff68acb98ec95277b361ee43@riseup.net \
--to=swedebugia@riseup.net \
--cc=gabrielhondet@gmail.com \
--cc=guix-devel@gnu.org \
/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).