From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] heirloom-mailx: add license info
Date: Sat, 13 Sep 2014 21:43:29 +0300 [thread overview]
Message-ID: <20140913184329.GA11424@tarshish> (raw)
In-Reply-To: <1410584439-31668-1-git-send-email-danomimanchego123@gmail.com>
Hi Danomi,
On Sat, Sep 13, 2014 at 01:00:39AM -0400, Danomi Manchego wrote:
> Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com>
> ---
> package/heirloom-mailx/heirloom-mailx.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/heirloom-mailx/heirloom-mailx.mk b/package/heirloom-mailx/heirloom-mailx.mk
> index 75221d4..0a80a3c 100644
> --- a/package/heirloom-mailx/heirloom-mailx.mk
> +++ b/package/heirloom-mailx/heirloom-mailx.mk
> @@ -7,6 +7,8 @@
> HEIRLOOM_MAILX_VERSION = 12.5
> HEIRLOOM_MAILX_SOURCE = heirloom-mailx_$(HEIRLOOM_MAILX_VERSION).orig.tar.gz
> HEIRLOOM_MAILX_SITE = http://snapshot.debian.org/archive/debian/20110427T035506Z/pool/main/h/heirloom-mailx
> +HEIRLOOM_MAILX_LICENSE = BSD-4c, Bellcore (base64), IEEE (docs), OpenVision (imap_gssapi), RSA Data Security (md5), Network Working Group (hmac), MPLv1.1 (nss)
Do we install these IEEE licensed docs? If not I think we can omit this
license. IANAL, though.
baruch
> +HEIRLOOM_MAILX_LICENSE_FILES = COPYING
>
> ifeq ($(BR2_PACKAGE_OPENSSL),y)
> HEIRLOOM_MAILX_DEPENDENCIES += openssl
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-09-13 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 5:00 [Buildroot] [PATCH] heirloom-mailx: add license info Danomi Manchego
2014-09-13 18:43 ` Baruch Siach [this message]
2014-09-13 19:51 ` Peter Korsgaard
2014-09-13 19:51 ` Danomi Manchego
2014-09-13 19:51 ` 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=20140913184329.GA11424@tarshish \
--to=baruch@tkos.co.il \
--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