unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Declan Tsien <declantsien@riseup.net>
To: Bruno Victal <mirai@makinata.eu>
Cc: 60752@debbugs.gnu.org
Subject: [bug#60752] [PATCH] services: connman: Add iwd backend support.
Date: Thu, 12 Jan 2023 23:22:04 +0800	[thread overview]
Message-ID: <871qnzwzfn.fsf@riseup.net> (raw)
In-Reply-To: <b263b300-a3c5-f579-45b5-c72cc7f9466e@makinata.eu>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Bruno Victal <mirai@makinata.eu> writes:

> On 2023-01-12 14:31, Declan Tsien wrote:
>> Bruno Victal <mirai@makinata.eu> writes:
>> 
>>>
>>> IMO if that's not the case, neither iwd nor wpa-supplicant backends should be pulled by connman. (or at least they should be required only if they are present among the services field)
>>> This is because not every machine comes or wants to use a wireless adapter.
>>>
>> 
>> Right, are you suggesting removing wpa-supplicant from requirement
>> field?
>
> If that's possible, yes.

I think that is a question for people with more knowledge in this regard.

But to my experiencing using connman and iwd. I think it's OK.
Now I am running these two shepherd services separately

- connman (without wpa-supplicant and iwd)
- iwd

This patch can be closed without applying.

Thanks for clarifying things for me.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]

  reply	other threads:[~2023-01-12 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874jstc3zl.fsf@riseup.net>
2023-01-12 12:56 ` [bug#60752] [PATCH] services: connman: Add iwd backend support Declan Tsien
2023-01-12 14:12   ` Bruno Victal
2023-01-12 14:31     ` Declan Tsien
2023-01-12 14:53       ` Bruno Victal
2023-01-12 15:22         ` Declan Tsien [this message]
2023-01-14  1:17   ` [bug#60752] [Declan Tsien] Re: [bug#60752] [PATCH] services: connman: Add option to disable wpa-supplicant Declan Tsien
2023-01-14  1:54   ` bug#60752: Declan Tsien
2023-01-16 17:22     ` bug#60752: Andrew Tropin
2023-01-17  0:30       ` [bug#60752] Declan Tsien

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=871qnzwzfn.fsf@riseup.net \
    --to=declantsien@riseup.net \
    --cc=60752@debbugs.gnu.org \
    --cc=mirai@makinata.eu \
    /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).