From: Jack Hill <jackhill@jackhill.us>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Tanguy LE CARROUR <tanguy@bioneland.org>, 52075@debbugs.gnu.org
Subject: [bug#52075] [PATCH 3/4] gnu: Add python-notmuch2.
Date: Wed, 24 Nov 2021 12:41:53 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2111241233290.13935@marsh.hcoop.net> (raw)
In-Reply-To: <87y25dqy08.fsf@nicolasgoaziou.fr>
On Wed, 24 Nov 2021, Nicolas Goaziou wrote:
> Hello,
>
> Jack Hill <jackhill@jackhill.us> writes:
>
>> As far as appropriate, do you know more about the origin of these
>> "notmuch2" bindings? I know that at some point notmuch upstream
>> re-wrote the binding using CFFI. Is that the origin of this package?
>> If so, then I would be inclined to make this package independent of
>> the existing python-notmuch package. If not, then please ignore this
>> concern.
>
> I do not grasp your concern. python-notmuch and python-notmuch2 share
> most fields. Inheritance prevents duplication, that's all.
>
> Why are you inclined to make this new package independant (in the sense
> of Guix inheritance) of python-notmuch?
It is possible that my concern was misplaced. My thinking was that if the
two bindings were logically separate projects, rather than being
variations on the same code, we should keep them logically separate in
Guix even if they are superficially similar. However, it might not be a
logically separate project, and that might not be the right way to think
about it anyway.
I don't have an objection to the version using inheritance. I am still
curious in learning about the differences between the two packages if only
for my own edification.
Hopefully that clarifies, and sorry for adding noise to this review.
Best,
Jack
next prev parent reply other threads:[~2021-11-24 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 9:57 [bug#52075] [PATCH 0/4] gnu: alot: Update to 0.10 Tanguy Le Carrour
2021-11-24 10:00 ` [bug#52075] [PATCH 1/4] gnu: python-urwidtrees: Update to 1.0.3 Tanguy Le Carrour
2021-11-24 10:00 ` [bug#52075] [PATCH 2/4] gnu: notmuch: Update to 0.34.1 Tanguy Le Carrour
2021-11-24 10:00 ` [bug#52075] [PATCH 3/4] gnu: Add python-notmuch2 Tanguy Le Carrour
2021-11-24 10:29 ` Nicolas Goaziou
2021-11-24 12:44 ` Tanguy LE CARROUR
2021-11-24 13:21 ` Nicolas Goaziou
2021-11-24 16:53 ` Jack Hill
2021-11-24 17:11 ` Nicolas Goaziou
2021-11-24 17:41 ` Jack Hill [this message]
2021-11-27 9:15 ` bug#52075: " Nicolas Goaziou
2021-11-28 17:32 ` [bug#52075] " Tanguy LE CARROUR
2021-11-24 10:00 ` [bug#52075] [PATCH 4/4] gnu: alot: Update to 0.10 Tanguy Le Carrour
2021-11-24 14:00 ` [bug#52075] [PATCH v2 1/4] gnu: python-urwidtrees: Update to 1.0.3 Tanguy Le Carrour
2021-11-24 14:00 ` [bug#52075] [PATCH v2 2/4] gnu: notmuch: Update to 0.34.1 Tanguy Le Carrour
2021-11-24 14:00 ` [bug#52075] [PATCH v2 3/4] gnu: Add python-notmuch2 Tanguy Le Carrour
2021-11-24 14:00 ` [bug#52075] [PATCH v2 4/4] gnu: alot: Update to 0.10 Tanguy Le Carrour
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=alpine.DEB.2.21.2111241233290.13935@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=52075@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=tanguy@bioneland.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).