unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, "Ludovic Courtès" <ludovic.courtes@inria.fr>,
	"Guix Devel" <guix-devel@gnu.org>
Subject: Re: Accuracy of importers?
Date: Thu, 28 Oct 2021 07:38:12 -0400	[thread overview]
Message-ID: <741B74BD-D4F6-45A6-A068-461ED8EB5AE7@lepiller.eu> (raw)
In-Reply-To: <878ryd8we4.fsf@inria.fr>

Le 28 octobre 2021 03:02:27 GMT-04:00, "Ludovic Courtès" <ludovic.courtes@inria.fr> a écrit :
>Hello Guix!
>
>As I’m preparing my PackagingCon talk and wondering how language package
>managers could make our lives easier, I thought it’d be interesting to
>know how well our importers are doing.
>
>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
>
>   gnu          90% (doesn’t know about dependencies)
>   pypi         50% (some miss source distro, “sdist”; some have
>                     non-Python deps)
>   cpan         ?
>   hackage      ?
>   stackage     (Lars?)
>   egg          (Xinglu?)
>   elpa         (Nicolas?)
>   gem          ?
>   go           (Sarah? Leo? Raghav?)
>   cran         5% (Ricardo? Simon? seems to almost always work?)
>   crate        10% (Efraim?)
>   texlive      (Ricardo? Thiago? Marius?)
>   opam         (Julien?)

I find it pretty good, when importing huge numbers of packages recently, I was able to build all of them without modification. However, lots rely on a github tarball, so I would change the source in these cases before sending them to guix.

>   minetest     (Maxime? Vivien?)
>   julia (WIP)  (Simon?)
>   npm (WIP)    (Jelle? Timothy?)
>
>(Lower is better.)  What would be your estimate?  
>
>Among those, which importers provide source that differs from what you’d
>get from upstream’s checkout or release tarballs?  My guess:
>
>   pypi (see LastPyMile paper)
>   elpa (gives hosted tarballs that can differ from upstream repo)
>   gem (similar to PyPI)
>   npm (ditto)
>
>What about licensing info: which ones provide accurate licensing info?
>My guess:
>
>   gnu
>   pypi
>   cpan
>   cran
>   elpa
>   go (?)
>   cran
>   crate (?)
>   texlive
>   opam (?)
>   minetest (?)
>
>TIA! :-)
>
>Ludo’.
>



  parent reply	other threads:[~2021-10-28 11:39 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
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 [this message]
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=741B74BD-D4F6-45A6-A068-461ED8EB5AE7@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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).