From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: NetworkManager: Set elogind on by default.
Date: Sun, 08 Sep 2019 04:13:16 +0200 [thread overview]
Message-ID: <20190908021316.3jkuSiFvxuYXNmYIeVi9zA67QRdSLzqn6IPcci9WHX8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14277@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
New comment by thomas-t-w on void-packages repository
https://github.com/void-linux/void-packages/pull/14277#issuecomment-529162605
Comment:
Hi,
I really appreciate your concern on this because it is important. I also use command line only systems with Network Manager. This build time option only adds a build time dependency. I tested a system without elogind with this build option on briefly and I was still able to connect to networks. I will admit that my tests were not extensive. If there are regressions for systems without elogind, I agree that we should revert it but from what I could tell, it still runs correctly even if elogind is not on the system. Can you test this with your use case and let me know if things work?
next prev parent reply other threads:[~2019-09-08 2:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 23:53 [PR PATCH] t voidlinux-github
2019-09-06 23:55 ` t voidlinux-github
2019-09-08 0:44 ` NetworkManager: Set elogind on by default voidlinux-github
2019-09-08 0:59 ` voidlinux-github
2019-09-08 2:13 ` voidlinux-github [this message]
2019-09-08 2:34 ` voidlinux-github
2019-09-08 13:24 ` voidlinux-github
2019-09-08 15:09 ` voidlinux-github
2019-09-09 12:15 ` voidlinux-github
2019-09-09 12:46 ` voidlinux-github
2019-09-09 13:44 ` voidlinux-github
2019-09-09 14:07 ` voidlinux-github
2019-09-09 14:12 ` voidlinux-github
2019-09-09 14:47 ` voidlinux-github
2019-09-11 11:42 ` [PR PATCH] [Merged]: " voidlinux-github
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190908021316.3jkuSiFvxuYXNmYIeVi9zA67QRdSLzqn6IPcci9WHX8@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).