From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45984@debbugs.gnu.org
Subject: [bug#45984] [PATCH 0/5] Fix recursive importers
Date: Wed, 27 Jan 2021 00:16:35 +0100 [thread overview]
Message-ID: <86im7ji90s.fsf@gmail.com> (raw)
In-Reply-To: <87ft2nwd3b.fsf@gnu.org>
Hi Ludo,
Thanks for the review.
On Tue, 26 Jan 2021 at 23:24, Ludovic Courtès <ludo@gnu.org> wrote:
>> $ guix import gem do-not-exist -r
>> #f
>>
>> $ ./pre-inst-env guix import gem do-not-exist -r
>> guix import: error: failed to download meta-data for package 'do-not-exist'
>
> I think we do want this error message. Why should we ignore
> non-existent packages when doing ‘-r’? It would think they’re still a
> problem, no?
Do you mean instead of displaying an error about the query (what the
patch does), displaying which dependent package has failed? Something
along these lines:
$ ./pre-inst-env guix import gem foo -r
guix import: error: failed to download meta-data for package 'bar'
If it is what you have in mind, it needs to really re-think how
’recursive-import’ works. Not only fixing the corner case. :-)
>> If I understand correctly, then the way the errors are reported could be
>> uniformized between all the importers, and maybe the snippet in the subcommands
>> "guix import <from>" could be refactorized a bit.
>
> Probably. ‘-r’ started as an option specific to one importer, but now
> that most of them (?) support it, it’d make sense to rethink the
> interfaces.
If we agree on the first part (the function argument “#:key
repo->guix-package” provided to ’recursive-import’ should always return
’values’), then let rethink the interface and how the errors are
handled.
Cheers,
simon
next prev parent reply other threads:[~2021-01-26 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 15:45 [bug#45984] [PATCH 0/5] Fix recursive importers zimoun
2021-01-19 15:47 ` [bug#45984] [PATCH 1/5] import: pypi: Return 'values' zimoun
2021-01-19 15:47 ` [bug#45984] [PATCH 2/5] import: hackage: " zimoun
2021-01-19 15:47 ` [bug#45984] [PATCH 3/5] import: elpa: " zimoun
2021-01-19 15:47 ` [bug#45984] [PATCH 4/5] import: cran: " zimoun
2021-01-19 15:47 ` [bug#45984] [PATCH 5/5] scripts: import: gem: Fix recursive error handling zimoun
2021-01-26 22:24 ` [bug#45984] [PATCH 0/5] Fix recursive importers Ludovic Courtès
2021-01-26 23:16 ` zimoun [this message]
2021-01-28 13:22 ` Ludovic Courtès
2021-01-28 22:07 ` zimoun
2022-03-07 21:52 ` bug#45984: " Ludovic Courtès
2022-03-08 8:36 ` [bug#45984] " zimoun
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=86im7ji90s.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=45984@debbugs.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).