all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: swedebugia@riseup.net
Cc: gabrielhondet@gmail.com, guix-devel <guix-devel@gnu.org>
Subject: Re: Stating the size of ecosystems in descriptions (Was: Re: Gauche description)
Date: Wed, 16 Jan 2019 13:53:21 +0100	[thread overview]
Message-ID: <87imyo7ohq.fsf@ambrevar.xyz> (raw)
In-Reply-To: <9b157f660f14ccf542cfa4fe793cc3db@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 414 bytes --]

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.

Alternatively, we could point at the web index of the packages.
E.g. 
- Pypi: https://pypi.org/
- Gauche: http://practical-scheme.net/wiliki/wiliki.cgi?Gauche%3aPackages
etc.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-01-16 12:53 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 [this message]
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             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imyo7ohq.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=gabrielhondet@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.