From: "Ludovic Courtès" <ludo@gnu.org>
To: Morgan.J.Smith@outlook.com
Cc: 58074@debbugs.gnu.org
Subject: [bug#58074] [PATCH] gnu: Add cyrus-sasl-xoauth2.
Date: Thu, 06 Oct 2022 22:47:48 +0200 [thread overview]
Message-ID: <87ilkwhe6j.fsf@gnu.org> (raw)
In-Reply-To: <DM5PR03MB31637C2C7C30C6360865EEBBC5539@DM5PR03MB3163.namprd03.prod.outlook.com> (Morgan J. Smith's message of "Sun, 25 Sep 2022 11:15:22 -0400")
Hi,
Morgan.J.Smith@outlook.com skribis:
> From: Morgan Smith <Morgan.J.Smith@outlook.com>
>
> * gnu/packages/cyrus-sasl.scm (cyrus-sasl-xoauth2): New variable.
LGTM, modulo two things:
> + (native-search-paths
> + (list (search-path-specification
> + (variable "SASL_PATH")
> + (files (list "lib/sasl2")))))
I believe this search path belongs in cyrus-sasl (see
<https://guix.gnu.org/manual/devel/en/html_node/Search-Paths.html>).
Could you provide a patch that does that? However, due to the number of
dependents of cyrus-sasl, this change will have to go on ‘staging’.
> + (home-page "https://github.com/moriyoshi/cyrus-sasl-xoauth2")
> + (synopsis "XOAUTH2 plugin for Cyrus SASL")
> + (description "Adds support for XOAUTH2 authentication to Cyrus SASL. Can
> +be used with isync to fetch mail from servers that support it.")
Please write full sentences.
Thanks in advance,
Ludo’.
next prev parent reply other threads:[~2022-10-06 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 15:15 [bug#58074] [PATCH] gnu: Add cyrus-sasl-xoauth2 Morgan.J.Smith
2022-10-06 20:47 ` Ludovic Courtès [this message]
2022-12-23 19:27 ` [bug#58074] [PATCH staging v3 1/2] gnu: cyrus-sasl: Set SASL_PATH to find plugins Reily Siegel
2022-12-23 19:27 ` [bug#58074] [PATCH staging v3 2/2] gnu: Add cyrus-sasl-xoauth2 Reily Siegel
2024-02-12 18:48 ` [bug#58074] [PATCH staging v3 1/2] gnu: cyrus-sasl: Set SASL_PATH to find plugins Samuel Fadel
2022-12-23 19:27 ` [bug#58074] [PATCH staging v2 " Morgan.J.Smith
2024-03-15 14:46 ` [bug#58074] [PATCH] gnu: Add cyrus-sasl-xoauth2 Zac Berkowitz
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=87ilkwhe6j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58074@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
/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).