From: Saul Wold <sgw@linux.intel.com>
To: rongqing.li@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] btrfs-tools: Add dependency on lzo acl e2fsprog
Date: Mon, 26 Aug 2013 07:37:20 -0700 [thread overview]
Message-ID: <521B6820.1000000@linux.intel.com> (raw)
In-Reply-To: <77319aeee8a2f49fa9ece78c4a0e4e20be3d4165.1377505592.git.rongqing.li@windriver.com>
Why?
And should the acl be controlled by a PACKAGECONFIG? Can it be disabled
during do_configure?
Sau!
On 08/26/2013 01:56 AM, rongqing.li@windriver.com wrote:
> From: "Roy.Li" <rongqing.li@windriver.com>
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
> meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
> index 07e8529..3ec9e8a 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
> @@ -10,7 +10,7 @@ HOMEPAGE = "https://btrfs.wiki.kernel.org"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=fcb02dc552a041dee27e4b85c7396067"
> SECTION = "base"
> -DEPENDS = "util-linux attr"
> +DEPENDS = "util-linux attr e2fsprogs lzo acl"
>
> SRCREV = "194aa4a1bd6447bb545286d0bcb0b0be8204d79f"
> SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git;protocol=git"
>
next prev parent reply other threads:[~2013-08-26 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 8:56 [PATCH 0/1] btrfs-tools: Add dependency on lzo acl e2fsprog rongqing.li
2013-08-26 8:56 ` [PATCH 1/1] " rongqing.li
2013-08-26 14:37 ` Saul Wold [this message]
2013-08-27 1:19 ` Rongqing Li
2013-08-28 0:34 ` Saul Wold
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=521B6820.1000000@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.