<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Thomas.<br>
<br>
I agree about finding the balance.<br>
<br>
Regarding this specific matter, having an visual indication of the
support or not for the new standard of the wireless support seems an
important issue for me.<br>
<br>
Having an message inside the help doesn't seems a good solution for
me, since it's not a "side" feature of wpa_supplicant. I would like
the LIBNL to be selected by wpa_supplicant, but I understand you are
not agree with this option<br>
<br>
I sent an V2 version of my patch, with an better indication of the
link between libnl and wpa_supplicant.<br>
<br>
If it doesn't work for you, I will send an patch with an indication
on the help message, but IMHO, at least, this suboption is
mandatory. <br>
<br>
Best regards <br>
<div class="moz-cite-prefix">On 08/08/2014 01:41 AM, Thomas
Petazzoni wrote:<br>
</div>
<blockquote cite="mid:20140808104151.6c0e08fb@free-electrons.com"
type="cite">
<pre wrap="">Dear Jean-Baptiste Theou,
On Thu, 7 Aug 2014 13:52:33 -0700, Jean-Baptiste Theou wrote:
</pre>
<blockquote type="cite">
<pre wrap="">IMHO, wpa_supplicant should provide the support of NL80211 by default
('depends on BR2_PACKAGE_LIBNL) since it's the new standard.
I wasn't expected to have to select LIBNL manually.
</pre>
</blockquote>
<pre wrap="">
There is a balance to find between:
* Adding suboptions to package to enable support for optional features
(what you did).
Advantages : more obvious to the user, you can enable an optional
feature in package A, but not in package B (like you can use OpenSSL
support for your web server, but not necessarily for all other
packages in your system)
Drawbacks : maintenance burden due to more Config.in options all
over the place.
* Make packages automatically enable optional features when the
necessary dependencies are available.
Advantages : less Config.in options to add everywhere.
Drawbacks : less obvious to the user, less flexible (enabling
OpenSSL makes it used in all packages that can optionally use it).
You could propose a patch that extends the Config.in help text of
wpa_supplicant to indicate this optional dependency, though we don't
have a specific policy about this.
Best regards,
Thomas
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<img src="cid:part1.02040206.07020103@adeneo-embedded.us"
border="0"></div>
</body>
</html>