From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, myglc2 <myglc2@gmail.com>
Subject: Re: [PATCH] gnu: r: Update to 3.3.1.
Date: Mon, 01 Aug 2016 23:20:13 +0200 [thread overview]
Message-ID: <87h9b4i3ua.fsf@gnu.org> (raw)
In-Reply-To: <874m745kci.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 01 Aug 2016 22:02:05 +0200")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> This obviously depends on the quality of the importers, but I think it
> wouldn’t take much effort to make this a reality. The main problem with
> offering magic like this is that it must be reliable or else it would
> just be frustrating users.
It’s indeed doable (we just need to generate a <package> on the fly,
which is essentially what importers do), and was part of the plan.
But as you note, the likely problem is that some packages won’t build,
for instance because we have incomplete or inaccurate dependency
information, and may be poorly integrated.
Nevertheless it’s worth trying!
Ludo’.
next prev parent reply other threads:[~2016-08-01 21:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 14:36 [PATCH] gnu: r: Update to 3.3.1 Roel Janssen
2016-07-30 19:41 ` myglc2
2016-07-30 22:55 ` Ludovic Courtès
2016-07-31 16:47 ` myglc2
2016-07-31 4:09 ` Pjotr Prins
2016-07-31 9:45 ` Roel Janssen
2016-07-31 17:49 ` myglc2
2016-08-01 6:00 ` Pjotr Prins
2016-08-01 17:17 ` myglc2
2016-08-01 19:44 ` Roel Janssen
2016-08-01 20:14 ` myglc2
2016-08-02 8:31 ` Roel Janssen
2016-08-01 20:02 ` Ricardo Wurmus
2016-08-01 20:59 ` myglc2
2016-08-02 6:00 ` Ricardo Wurmus
2016-08-01 21:20 ` Ludovic Courtès [this message]
2016-08-02 3:50 ` Pjotr Prins
2016-08-02 5:53 ` Ricardo Wurmus
2016-07-31 17:12 ` myglc2
2016-07-31 17:34 ` Roel Janssen
2016-07-31 8:04 ` Andreas Enge
2016-08-01 8:26 ` 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
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=87h9b4i3ua.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=rekado@elephly.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).