From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 37369@debbugs.gnu.org, Divan Santana <divan@santanas.co.za>,
help-guix@gnu.org
Subject: Re: bug#37369: Getting network-manager-openconnect to work
Date: Wed, 11 Sep 2019 13:39:46 +0200 [thread overview]
Message-ID: <20190911113946.5mxaxerhjkuejtel@pelzflorian.localdomain> (raw)
In-Reply-To: <20190911073822.GI977@E5400>
On Wed, Sep 11, 2019 at 10:38:22AM +0300, Efraim Flashner wrote:
> Instead of adding openconnect to network-manager, would it be enough to
>
> (substitute* "the-file"
> (("/usr/sbin/openconnect") "openconnect"))
>
>
No, at least the comment documenting nm_utils_file_search_in_paths says:
/**
* nm_utils_file_search_in_paths:
* […]
* @try_first: (allow-none): a custom path to try first before searching.
* It is silently ignored if it is empty or not an absolute path.
* […]
I do not know if my patch works though.
Regards,
Florian
next prev parent reply other threads:[~2019-09-11 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 9:57 Getting network-manager-openconnect to work Divan Santana
2019-09-10 11:21 ` pelzflorian (Florian Pelz)
2019-09-11 7:38 ` bug#37369: " Efraim Flashner
2019-09-11 11:39 ` pelzflorian (Florian Pelz) [this message]
2019-09-11 20:46 ` Ludovic Courtès
2019-09-12 5:34 ` pelzflorian (Florian Pelz)
2019-09-16 15:57 ` Ludovic Courtès
2019-09-16 16:06 ` pelzflorian (Florian Pelz)
2019-09-27 16:37 ` bug#37369: " pelzflorian (Florian Pelz)
2019-09-28 14:00 ` Divan Santana
2019-09-28 14:16 ` Divan Santana
2019-09-28 15:34 ` pelzflorian (Florian Pelz)
2019-09-29 7:54 ` pelzflorian (Florian Pelz)
2019-09-28 16:47 ` pelzflorian (Florian Pelz)
2019-10-03 11:51 ` Divan Santana
2019-09-16 11:53 ` pelzflorian (Florian Pelz)
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=20190911113946.5mxaxerhjkuejtel@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=37369@debbugs.gnu.org \
--cc=divan@santanas.co.za \
--cc=efraim@flashner.co.il \
--cc=help-guix@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.
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).