all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adopt a patch!
Date: Mon, 18 Sep 2017 12:45:58 +0200	[thread overview]
Message-ID: <87vakgthcp.fsf@elephly.net> (raw)
In-Reply-To: <87d16pf5x5.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hi Arun,
> What is more scary is massive imports from external repos (CPAN, etc.).
> I think we cannot handle all of it, not with our “quality” guidelines
> and not with the pace at which these repos change.
>
> At the GHM, we were discussing that, probably, we’ll have to accept for
> Guix to be a gateway to those repos (at least for the “non-core” subsets
> of the repos).  Concretely, one could do “guix package -i cpan!Foo::Bar”
> and have the package DAG imported and built live.  It’s either that or
> people will use CPAN’s own tools to achieve this.

Unfortunately, this cannot be done for all packages from CPAN, because
many of these packages are used as inputs for other packages that cannot
be installed through importers.

For CRAN updates we’re doing pretty well, I think, but we will certainly
need to improve our update efforts for packages from CPAN and Hackage.

I would like to exclude leaf packages from these repositories in the
future (once the importers become more usable for non-developers), but
I’m not sure that this would help much for all the packages we have
added as inputs for non-importable packages.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-09-18 10:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11  8:13 Adopt a patch! Ludovic Courtès
2017-09-14  1:22 ` Arun Isaac
2017-09-14  4:26   ` ng0
     [not found] ` <4fecd5dd.AEQAQDR72NkAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZudnG@mailjet.com>
2017-09-17 20:04   ` Ludovic Courtès
2017-09-18 10:45     ` Ricardo Wurmus [this message]
2017-09-19 14:15     ` Maxim Cournoyer
2017-09-19 14:22     ` Arun Isaac
2017-09-20  5:21       ` Pjotr Prins
2017-09-20  6:11         ` ng0
2017-09-21  9:37         ` Arun Isaac
2017-09-21 11:25           ` Adonay Felipe Nogueira
2017-09-21 16:33             ` ng0
2017-09-20 11:48       ` Hartmut Goebel
2017-09-21 14:08         ` Ricardo Wurmus
2017-09-21 14:39           ` Maxim Cournoyer
2017-09-21 16:16             ` Adonay Felipe Nogueira
2017-09-21 20:31             ` Ricardo Wurmus
2017-09-22  5:02               ` Pjotr Prins
2017-09-22 12:15                 ` Kei Kebreau
2017-09-22 10:42               ` Thomas Danckaert
2017-09-22 14:22                 ` Ludovic Courtès
2017-10-14 21:26                   ` ng0
2017-09-22 19:45                 ` Maxim Cournoyer
2017-09-23 19:51                   ` Thomas Danckaert
2017-09-22  9:10           ` Hartmut Goebel
     [not found]     ` <3db6934a.AEQAQWrlP5MAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZwSg8@mailjet.com>
2017-10-13 13:08       ` Ludovic Courtès

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=87vakgthcp.fsf@elephly.net \
    --to=rekado@elephly.net \
    --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 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.