Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8936] Aircrack-ng - Alot of missing dependencies
Date: Wed, 18 May 2016 19:02:28 +0000	[thread overview]
Message-ID: <bug-8936-163-ZGqJzIGKSJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8936-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=8936

Arnout Vandecappelle <arnout@mind.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #2 from Arnout Vandecappelle <arnout@mind.be> ---
aircrack-ng is a toolbox with several tools. Not all of them require iw,
iwconfig, etc. It is possible that some users only require the tools that don't
use these.

That said, it would make sense to mention that explicitly in the help text.
I'll submit a patch doing exactly that.

But I'm marking this bug as WONTFIX because we will not select ethtools, iw,
etc.

If you disagree, feel free to reopen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2016-05-18 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 11:57 [Buildroot] [Bug 8936] New: Aircrack-ng - Alot of missing depencies bugzilla at busybox.net
2016-05-18 11:57 ` [Buildroot] [Bug 8936] Aircrack-ng - Alot of missing dependencies bugzilla at busybox.net
2016-05-18 12:16 ` bugzilla at busybox.net
2016-05-18 19:02 ` bugzilla at busybox.net [this message]

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=bug-8936-163-ZGqJzIGKSJ@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox