From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Julien Lepiller <julien@lepiller.eu>,
51091@debbugs.gnu.org, Xinglu Chen <public@yoctocell.xyz>
Subject: [bug#51091] [PATCH v3] guix: opam: Do not fail when refreshing.
Date: Fri, 19 Nov 2021 10:40:11 +0100 [thread overview]
Message-ID: <CAJ3okZ2k6XtZzb1hVFMBG5LpY8iS7rLXnkoDSUynAQAccH7mrg@mail.gmail.com> (raw)
In-Reply-To: <87czmwo68f.fsf@gnu.org>
Hi Ludo and Julien,
On Fri, 19 Nov 2021 at 10:17, Ludovic Courtès <ludo@gnu.org> wrote:
> I’m fine either way. I think there’s value longer-term in having
> structured exceptions in importers, though.
Yes, I agree. For instance, as discussed after this old quick fix
[1]. Then I did some pair programming with jeko to have a v2. The
idea is to have a common exception mechanism for all the importers.
Instead of case per case and scattered implementation through various
importers (proposed patch for opam, another example
guix/import/elpa.scm using &message etc.). All the importers should
share the same interface for handling exceptions and errors. Well, it
has never seen the light because time flies so fast and because at one
point, one needs to sit down and unknot all; personally, I have been a
bit lazy for completing the task. :-)
1: <http://issues.guix.gnu.org/issue/45984#9>
> Julien: your call!
I agree, as mentioned [2]. :-)
2: <http://issues.guix.gnu.org/issue/51888#3>
Cheers,
simon
next prev parent reply other threads:[~2021-11-19 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 3:03 [bug#51091] [PATCH] guix: opam: Do not fail when refreshing Julien Lepiller
2021-10-09 9:39 ` Xinglu Chen
2021-10-14 13:01 ` Ludovic Courtès
2021-10-16 2:10 ` [bug#51091] [PATCH v2] " Julien Lepiller
2021-10-18 8:39 ` Ludovic Courtès
2021-11-19 1:16 ` [bug#51091] [PATCH v3] " Julien Lepiller
2021-11-19 1:43 ` zimoun
2021-11-19 9:16 ` Ludovic Courtès
2021-11-19 9:40 ` zimoun [this message]
2021-11-19 11:19 ` Julien Lepiller
2021-11-19 11:30 ` 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=CAJ3okZ2k6XtZzb1hVFMBG5LpY8iS7rLXnkoDSUynAQAccH7mrg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=51091@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=ludo@gnu.org \
--cc=public@yoctocell.xyz \
/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).