unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Accuracy of importers?
Date: Sat, 30 Oct 2021 17:49:55 +0200	[thread overview]
Message-ID: <86wnlujyvw.fsf@gmail.com> (raw)
In-Reply-To: <87ilxfwl2q.fsf@gnu.org>

Hi Ludo,

On Fri, 29 Oct 2021 at 23:57, Ludovic Courtès <ludo@gnu.org> wrote:

> (It’s quite expensive to run because it downloads a whole bunch of
> things and tries many 404 URLs in the case of CRAN before finding the
> right one.)

Ah… it requires investigation thus.


> --8<---------------cut here---------------start------------->8---
> $ SAMPLE_SIZE=200 ./pre-inst-env guile ~/src/guix-debugging/importer-accuracy.scm
> […]
> Accuracy for 'pypi' (200 packages):
>   accurate: 58 (29%)
>   different inputs: 142 (71%)
>   different source: 0 (0%)
>   inconclusive: 0 (0%)
> Accuracy for 'cran' (200 packages):
>   accurate: 176 (88%)
>   different inputs: 23 (12%)
>   different source: 1 (0%)
>   inconclusive: 0 (0%)
> --8<---------------cut here---------------end--------------->8---

[...]

> The script doesn’t do anything useful for crates because they have their
> own way of representing inputs.  It doesn’t account for changes in
> ‘arguments’ like zimoun suggested, meaning it’s overestimating
> accuracy.

It is already quite interesting results.  Because it shows upstream
stability, IIUC.  Well, it means that running “guix import pypi” one
months ago and running the sames now, 71% packages have different
inputs.  Right?  It is because some metadata from PyPI changed, right?
Not because “guix import pypi” was doing wrong and now it does better,
right?

IMHO, it shows how PyPI allows bad practises about packaging, isn’t it?

My understanding of this experiment is about upstream “quality”, not
about importer “accuracy”.  Do I incorrectly understand?


Cheers,
simon


  reply	other threads:[~2021-10-30 16:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28  7:02 Accuracy of importers? Ludovic Courtès
2021-10-28  8:17 ` Lars-Dominik Braun
2021-10-28  8:54   ` Ludovic Courtès
2021-10-28 10:06     ` Lars-Dominik Braun
2021-10-29 21:57   ` Ludovic Courtès
2021-10-30 15:49     ` zimoun [this message]
2021-11-09 16:48       ` Ludovic Courtès
2021-11-09 18:36         ` zimoun
2021-10-28  9:06 ` zimoun
2021-10-28  9:30   ` zimoun
2021-10-28 11:38 ` Julien Lepiller
2021-10-28 12:25 ` Ricardo Wurmus
2021-10-28 14:47 ` Katherine Cox-Buday
2021-10-29 19:29 ` Nicolas Goaziou
2021-10-29 23:08   ` Carlo Zancanaro
2021-10-30 10:55 ` Xinglu Chen

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=86wnlujyvw.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).