From: "Denys Dmytriyenko" <denis@denix.org>
To: meta-arm@lists.yoctoproject.org
Cc: nd@arm.com
Subject: Re: [meta-arm] [PATCH] Remove meta-arm-iota
Date: Thu, 20 Feb 2020 17:14:24 -0500 [thread overview]
Message-ID: <20200220221424.GH4735@denix.org> (raw)
In-Reply-To: <20200220150941.25282-1-jon.mason@arm.com>
On Thu, Feb 20, 2020 at 10:09:41AM -0500, Jon Mason wrote:
> Feedback received that it is not acceptable to have a distro layer
> inside (https://lists.yoctoproject.org/g/meta-arm/message/6). Removing
> from meta-arm and will create a separate git repository once that code
> is ready.
I don't think that was the message - as long as all your distro stuff is
isolated from bsp and the rest into its own layer, it should be fine. You
don't need to remove it completely into a separate repo.
--
Denys
> Change-Id: I74d1083341d90caa038c1bd8c1d53aa565d28460
> Signed-off-by: Jon Mason <jon.mason@arm.com>
> ---
> meta-arm-iota/conf/layer.conf | 13 -------------
> 1 file changed, 13 deletions(-)
> delete mode 100644 meta-arm-iota/conf/layer.conf
>
> diff --git a/meta-arm-iota/conf/layer.conf b/meta-arm-iota/conf/layer.conf
> deleted file mode 100644
> index 392ed9b..0000000
> --- a/meta-arm-iota/conf/layer.conf
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -# We have a conf and classes directory, add to BBPATH
> -BBPATH .= ":${LAYERDIR}"
> -
> -# We have recipes-* directories, add to BBFILES
> -BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
> - ${LAYERDIR}/recipes-*/*/*.bbappend"
> -
> -BBFILE_COLLECTIONS += "meta-arm-iota"
> -BBFILE_PATTERN_meta-arm-iota = "^${LAYERDIR}/"
> -BBFILE_PRIORITY_meta-arm-iota = "6"
> -
> -LAYERDEPENDS_meta-arm-iota = "core"
> -LAYERSERIES_COMPAT_meta-arm-iota = "warrior zeus"
> --
> 2.17.1
>
>
prev parent reply other threads:[~2020-02-20 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:09 [PATCH] Remove meta-arm-iota Jon Mason
2020-02-20 22:14 ` Denys Dmytriyenko [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=20200220221424.GH4735@denix.org \
--to=denis@denix.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.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.