From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] adding new package: reaver
Date: Wed, 11 Apr 2018 15:54:31 +0200 [thread overview]
Message-ID: <20180411155431.305335a9@windsurf> (raw)
In-Reply-To: <1523451771-29353-1-git-send-email-guillaume.bressaix@gmail.com>
Hello,
Thanks for this contribution. See below for some comments.
First, the commit title should be "reaver: new package"
On Wed, 11 Apr 2018 15:02:51 +0200, Guillaume W. Bres wrote:
> Generic autotools package, easy to cross-compile but it is mandatory
> to use the t6x github fork (latest Makefiles set).
What is the "t6x github fork" ?
> package/Config.in | 1 +
> package/reaver/Config.in | 8 ++++++++
> package/reaver/reaver.mk | 15 +++++++++++++++
Addition of an entry in the DEVELOPERS file is missing, and also the
hash file is missing. Could you add these ?
> diff --git a/package/reaver/Config.in b/package/reaver/Config.in
> new file mode 100644
> index 0000000..703fa28
> --- /dev/null
> +++ b/package/reaver/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_REAVER
> + bool "reaver"
> +
Unneeded empty new line.
> + select BR2_PACKAGE_LIBPCAP
> +
Ditto.
Also, could you test your package with ./utils/test-pkg, to make sure
it builds properly with some basic toolchain configurations ?
> + help
> + Reaver performs brute force attacks against WPS pin numbers.
> + It is recommended to use "Aircrack-ng" along reaver, but not necessary.
Lines are too long, they should be wrapped at 72 characters. If you
run ./utils/check-package package/reaver/* you will see a number of
warnings about your package. They should be fixed before submission.
Also, please add the URL of the upstream project in the Config.in help
text. See how it's done in other packages.
> diff --git a/package/reaver/reaver.mk b/package/reaver/reaver.mk
> new file mode 100644
> index 0000000..8e4e3c6
> --- /dev/null
> +++ b/package/reaver/reaver.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# reaver
> +#
> +################################################################################
> +
> +REAVER_VERSION = 9bae55bd30b6d46b42da3a09dc23c8b0f9341996
> +REAVER_SITE = $(call github,t6x,reaver-wps-fork-t6x,$(REAVER_VERSION))
> +REAVER_LICENSE = GPL-2.0+
> +REAVER_LICENSE_FILES = docs/LICENSE
> +
> +REAVER_SUBDIR = src
> +REAVER_INSTALL_TARGET = YES
This last line is not needed.
If you could fix those issues and submit an updated version, it would
be nice. Don't forget to use "git format-patch -v2" for the new
version, and add a changelog of what has been changed.
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-11 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 13:02 [Buildroot] [PATCH 1/1] adding new package: reaver Guillaume W. Bres
2018-04-11 13:54 ` Thomas Petazzoni [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=20180411155431.305335a9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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