From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] optional DBus support in wpa_supplicant
Date: Mon, 13 Jul 2009 20:26:30 +0200 [thread overview]
Message-ID: <87k52c1lt5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4A5B4D46.6010807@zacarias.com.ar> (Gustavo Zacarias's message of "Mon\, 13 Jul 2009 12\:05\:42 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Hi,
Gustavo> Being the one "guilty" of wpa_supplicant updates i don't
Gustavo> have a strong opinion on this either. On one side
Gustavo> wpa_supplicant has it's own way of controlling itself via
Gustavo> wpa_cli and thus somewhat negates the need for dbus
Gustavo> bindings. On the other side you may not want to fork to
Gustavo> call wpa_cli and/or learn the wpa_supplicant/cli controlling
Gustavo> protocol (or other good reasons), and if you already have
Gustavo> dbus enabled those extra 24k probably won't hurt that much
Gustavo> in the global scheme of things - after all people who want
Gustavo> to save that last KB will probably steer away from dbus.
Indeed. For big dependencies like dbus (or openssl), then I would
prefer BR to just do the right thing (tm) instead of adding very
detailed configuration options for things that only increase the size
with a few %.
In the case of dbus, the minimal configuration (including
dependencies) is around ~1MB, so I don't think it's worthwhile
discussing about 24kb overhead.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-07-13 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 8:20 [Buildroot] [PATCH] optional DBus support in wpa_supplicant Sven Neumann
2009-07-13 9:13 ` Sven Neumann
2009-07-13 10:44 ` Peter Korsgaard
2009-07-13 14:32 ` Sven Neumann
2009-07-13 15:05 ` Gustavo Zacarias
2009-07-13 18:26 ` Peter Korsgaard [this message]
2009-07-14 11:04 ` Sven Neumann
2009-07-14 19:20 ` Peter Korsgaard
2009-07-15 8:11 ` Sven Neumann
2009-07-20 11:39 ` Sven Neumann
2009-07-20 20:13 ` Peter Korsgaard
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=87k52c1lt5.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.