IWD no longer requires either openresolve or systemd for resolution it can now operate with a 3rd 'None' option. https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=b96bbb35e07a6bbd7035cd8fcab4e91c89626355 this landed in 1.11 currently the ebuild forces openresolve on USE=!systemd builds, it should allow for none ``` systemd? ( sys-apps/systemd ) !systemd? ( virtual/resolvconf ) ``` Reproducible: Always
I'm not sure we really need to support the use-case where "standalone" is enabled but without any DNS support. What USE flag setup would you imagine for this scenario? We certainly want DNS support here by default.
(In reply to Ben Kohler from comment #1) > I'm not sure we really need to support the use-case where "standalone" is > enabled but without any DNS support. What USE flag setup would you imagine > for this scenario? > > We certainly want DNS support here by default. I understand supporting DNS. But I'd prefer to not force the installation openresolve if the build dependency doesn't actually require it. Surely we can assume a gentoo user is capable of deciding for themselves, especially one running 'standalone'? Furthermore, the current use flag configuration presumes that openresolve and systemd are mutually exclusive, which isn't the case, Both can in fact exist on the same system. I'd rather not explore the assumption here where all systemd users use resolved. I can see two solutions 1. add openresolve use flag and rework `if not systemd` logic 2. drop `standalone` use flag and do not build iwd/main.conf for users in ebuild Personally I prefer 2, I don't think conf files should be built in this fashion IMHO I think making too many assumptions about a users configuration is dangerous and overall limits choice across gentoo. I hope you can find a solution here that's comfortable for you. Thanks
Advanced users can already hand-configure what I'm calling "standalone mode" without using the USE flag. This flag helps get all the necessary pieces in place automatically. I would suggest you just stop enabling that flag, if that's not what you're looking for.
your correct `-standalone` fixes the issue for me. I'll let you decide how and if you want to incorporate 'None' DNS resolution into your ebuild. Thanks
