From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.linuxtogo.org>
Subject: Re: [PATCH] socat: missing several dependencies
Date: Mon, 13 Aug 2012 09:54:57 +0300 [thread overview]
Message-ID: <5028A4C1.9080602@linux.intel.com> (raw)
In-Reply-To: <20120731185629.GA13766@windriver.com>
On 07/31/2012 09:56 PM, Amy Fong wrote:
> socat: missing several dependencies
>
> socat depends on ncurses, readline, and tcp-wrappers
>
> Signed-off-by: Amy Fong <amy.fong@windriver.com>
> ---
> socat_1.7.2.0.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-connectivity/socat/socat_1.7.2.0.bb b/meta/recipes-connectivity/socat/socat_1.7.2.0.bb
> index 1273dcf..0faf016 100644
> --- a/meta/recipes-connectivity/socat/socat_1.7.2.0.bb
> +++ b/meta/recipes-connectivity/socat/socat_1.7.2.0.bb
> @@ -4,7 +4,7 @@ HOMEPAGE = "http://www.dest-unreach.org/socat/"
>
> SECTION = "console/network"
>
> -DEPENDS = "openssl"
> +DEPENDS = "openssl readline ncurses tcp-wrappers"
>
I have been thinking on this one and trying to understand why we should
need to have readline and ncurses for socat, is there any configure
flags to disable these instead of depending on them?
It also seems that tcp-wrappers' libwrap is also optional and can be
disabled via the configure options. I can see value of libwrap here,
but we have not explicitly enabled it in the past, so my initial thought
here is to disable it instead of adding the DEPENDS.
Sau!
> LICENSE = "GPL-2.0+-with-OpenSSL-exception"
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
prev parent reply other threads:[~2012-08-13 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 18:56 [PATCH] socat: missing several dependencies Amy Fong
2012-08-13 6:54 ` Saul Wold [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=5028A4C1.9080602@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.linuxtogo.org \
--cc=openembedded-core@lists.openembedded.org \
/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