From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] httping: new package
Date: Sun, 13 Jan 2013 12:05:00 +0100 [thread overview]
Message-ID: <20130113120500.0ad7be3a@skate> (raw)
In-Reply-To: <1358036972-10406-1-git-send-email-gilles.talis@gmail.com>
Dear Gilles Talis,
On Sat, 12 Jan 2013 16:29:32 -0800, Gilles Talis wrote:
> Httping is like 'ping' but for http-requests.
>
> Fixed commit following review
Do not put such a comment in the commit. If you want to put a changelog
with the differences since the first posting, it should go...
>
> Signed-off-by: Gilles Talis <gilles.talis@gmail.com>
> ---
... here. I.e, after the "---" sign.
That's because we don't want the changelog to end up forever in the
Buildroot commit history.
> +if BR2_PACKAGE_HTTPING
> +
> +config BR2_PACKAGE_HTTPING_OPENSSL
> + bool "OpenSSL support"
> + depends on BR2_PACKAGE_OPENSSL
> + default y
> + help
> + Adds openSSL support to httping
I'd say it should rather be:
config BR2_PACKAGE_HTTPING_OPENSSL
bool "OpenSSL support"
select BR2_PACKAGE_OPENSSL
help
Adds OpenSSL support to httping
When we have sub-options to enable more features, we generally use
"select" to make sure that the needed libraries are brought in.
> +HTTPING_VERSION = 1.5.6
Any reason not to use 1.5.7.
> +HTTPING_SOURCE = httping-$(HTTPING_VERSION).tgz
> +HTTPING_SITE = http://www.vanheusden.com/httping
> +HTTPING_LICENSE = GPLv3
> +HTTPING_LICENSE_FILES = license.txt
Actually, the license seems to be GPLv2. If you look at this
license.txt file, it says:
The license of this program can be obtained from:
http://www.vanheusden.com/license.txt
And if you look at this other license.txt file, it contains the text of
GPLv2.
> +define HTTPING_BUILD_CMDS
> + $(MAKE) CC="$(TARGET_CC)" \
> + LD="$(TARGET_LD)" \
> + STRIP="$(TARGET_STRIP)" \
> + SSL=$(HTTPING_SSL) \
> + DEBUG=no \
> + TFO=$(HTTPING_TFO) -C $(@D)
> +endef
I saw your e-mail with your issues using TARGET_CONFIGURE_OPTS. But
there shouldn't be any issue doing:
define HTTPING_BUILD_CMDS
$(MAKE) $(TARGET_CONFIGURE_OPTS) \
SSL=$(HTTPING_SSL) \
DEBUG=no \
TFO=$(HTTPING_TFO) -C $(@D)
endef
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-13 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 0:29 [Buildroot] [PATCH 1/1] httping: new package Gilles Talis
2013-01-13 11:05 ` Thomas Petazzoni [this message]
2013-01-13 20:21 ` Gilles Talis
2013-01-13 20:32 ` Thomas Petazzoni
[not found] ` <CAKcgs2xk-=iG-3Ezmc1upEPBjhSGcmgg9WSwn=1E3+OKDT05fg@mail.gmail.com>
2013-01-14 0:47 ` Gilles Talis
2013-01-14 13:02 ` Peter Korsgaard
2013-01-19 13:51 ` Arnout Vandecappelle
2013-01-19 13:52 ` [Buildroot] [PATCH] httping: remove redundant 'override CFLAGS' patch Arnout Vandecappelle
2013-01-20 20:03 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 23:32 [Buildroot] [PATCH 1/1] httping: new package gilles.talis at gmail.com
2013-01-15 8:23 ` Peter Korsgaard
2013-01-12 0:00 gilles.talis at gmail.com
2013-01-12 11:07 ` Thomas Petazzoni
2013-01-12 16:37 ` Gilles Talis
2013-01-13 0:37 ` Gilles Talis
2013-01-19 13:39 ` Arnout Vandecappelle
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=20130113120500.0ad7be3a@skate \
--to=thomas.petazzoni@free-electrons.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