unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Accuracy of importers?
Date: Thu, 28 Oct 2021 10:54:14 +0200	[thread overview]
Message-ID: <87a6it7cnd.fsf@inria.fr> (raw)
In-Reply-To: <YXpcmp3+b9J3RLBp@noor.fritz.box> (Lars-Dominik Braun's message of "Thu, 28 Oct 2021 10:17:30 +0200")

Hi!

Lars-Dominik Braun <lars@6xq.net> skribis:

>> My understanding is that most of them require manual intervention—i.e.,
>> one has to tweak what ‘guix import’ produces, even if we ignore
>> synopsis/description/license, to set the right inputs, etc.  If we were
>> to estimate the fraction of imported packages for which manual changes
>> are needed, what would it look like?
>> 
>>    importer     fraction of imported packages needing changes
>>    pypi         50% (some miss source distro, “sdist”; some have
>>                      non-Python deps)
> that seems right, although the most common modification I do nowadays
> is replacing 'check with a pytest phase.

Right.  PyPI/setup.py/.whl doesn’t contain info as to how to run tests,
right?

>>    hackage      ?
>>    stackage     (Lars?)
> I’ve mostly used the updater, not the importer, so I can’t say a
> number unfortunately.

Did the updater suggest input changes?

>>    cran         5% (Ricardo? Simon? seems to almost always work?)
> In my experience the number of interventions here goes towards zero
> actually, except for description. It’s pretty good :)

Yay!

>>    npm (WIP)    (Jelle? Timothy?)
> Maybe 5%? But the imported packages do not build anything and don’t
> run tests either, so chances for failure are pretty low.

Yeah.

> Would it be possible to just run the importer again for existing packages
> and compare the result (minus synopsis/description) with what’s
> available in Guix? That should give you much more accurate numbers than
> our guesswork.

That’s a good idea.  I can try and do that on a sample of packages.

Thanks!

Ludo’.


  reply	other threads:[~2021-10-28  8:54 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 [this message]
2021-10-28 10:06     ` Lars-Dominik Braun
2021-10-29 21:57   ` Ludovic Courtès
2021-10-30 15:49     ` zimoun
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=87a6it7cnd.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.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).