From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/tripwire: new package
Date: Thu, 9 Jun 2016 23:57:06 +0200 [thread overview]
Message-ID: <20160609235706.2a697076@free-electrons.com> (raw)
In-Reply-To: <1461705192-15282-1-git-send-email-bernd.kuhls@t-online.de>
Hello,
On Tue, 26 Apr 2016 23:13:12 +0200, Bernd Kuhls wrote:
> + install-data-hook:
> +- prefix="$(prefix)" sysconfdir="$(sysconfdir)" \
> +- path_to_vi="$(path_to_vi)" path_to_sendmail="$(path_to_sendmail)" \
> +- ./install/install.sh
> ++ $(mkdir_p) $(DESTDIR)$(sbindir)
> ++ $(install_sh_SCRIPT) install/install.sh $(DESTDIR)$(sbindir)
Why are you changing the logic that runs install.sh on the build
machine to a logic that installs install.sh to the target? How can
installing install.sh on the target be useful?
> ++# prefix="$(prefix)" sysconfdir="$(sysconfdir)" \
> ++# path_to_vi="$(path_to_vi)" path_to_sendmail="$(path_to_sendmail)" \
> ++# ./install/install.sh
Please don't commend the code, just remove it.
Could you submit a bug upstream (they use Github, so it's trivial) to
ask them to make install.sh non-interactive ?
Also, isn't this install.sh script doing this that are also useful
(other than stupidly asking the user to explicitly accept the license).
> diff --git a/package/tripwire/Config.in b/package/tripwire/Config.in
> new file mode 100644
> index 0000000..1373bb6
> --- /dev/null
> +++ b/package/tripwire/Config.in
> @@ -0,0 +1,21 @@
> +config BR2_PACKAGE_TRIPWIRE
> + bool "tripwire"
> + depends on BR2_INSTALL_LIBSTDCPP
> + depends on BR2_USE_MMU # fork()
> + depends on BR2_USE_WCHAR
> + select BR2_PACKAGE_OPENSSL
OpenSSL is not mandatory. Use --enable-openssl / --disable-openssl to
make it optional in the .mk file.
> +TRIPWIRE_VERSION = 2.4.3.1
> +TRIPWIRE_SITE = $(call github,Tripwire,tripwire-open-source,$(TRIPWIRE_VERSION))
> +TRIPWIRE_LICENSE = GPLv2+
This license is a bit of an issue when OpenSSL support is enabled: the
GPL license and the OpenSSL license are incompatible, so you cannot
distribute a tripwire binary with OpenSSL support. They need to use a
GPL license with OpenSSL exception for the binary to be
redistributable. See
https://people.gnome.org/~markmc/openssl-and-the-gpl.html for details.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-09 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 21:13 [Buildroot] [PATCH v2 1/1] package/tripwire: new package Bernd Kuhls
2016-06-09 21:57 ` 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=20160609235706.2a697076@free-electrons.com \
--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