From: Nikolay Dimitrov <picmaster@mail.bg>
To: Ann Thornton <Ann.Thornton@freescale.com>,
Ann Thornton <ra43240@freescale.com>,
meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-demos][PATCH] New packagegroups to organize tools
Date: Mon, 13 Jul 2015 17:03:52 +0300 [thread overview]
Message-ID: <55A3C548.3020408@mail.bg> (raw)
In-Reply-To: <55A03A2C.8030605@freescale.com>
Hi Ann,
On 07/11/2015 12:33 AM, Ann Thornton wrote:
> On 7/10/2015 2:21 PM, Nikolay Dimitrov wrote:
>> Hi Ann,
>>
>> On 07/10/2015 09:32 PM, Ann Thornton wrote:
>>> The tools are grouped into core and extended with i.MX specific
>>> tools in a .bbappend file.
>>>
>>> Signed-off-by: Ann Thornton <ra43240@freescale.com>
>>> ---
>>> .../packagegroups/packagegroup-fsl-tools-core.bb | 39
>>> +++++++++++++++++
>>> .../packagegroup-fsl-tools-extended.bb | 45
>>> ++++++++++++++++++++
>>> .../packagegroup-fsl-tools-extended.bbappend | 13 ++++++
>>> 3 files changed, 97 insertions(+)
>>> create mode 100644
>>> recipes-fsl/packagegroups/packagegroup-fsl-tools-core.bb
>>> create mode 100644
>>> recipes-fsl/packagegroups/packagegroup-fsl-tools-extended.bb
>>> create mode 100644
>>> recipes-fsl/packagegroups/packagegroup-fsl-tools-extended.bbappend
>>
>> Just curious regarding the naming of packagegroup-fsl-tools-core: what
>> makes it FSL-specific?
>
> Nothing, really. Except that this is fsl-demos. Should it be named
> without the fsl?
I think it would be better this way. I also looked at the extended
packagegroup, and it can also go without the fsl.
I'm leaving the final choice to your discretion.
>
> Thanks for the comments!
> Ann
Regards,
Nikolay
next prev parent reply other threads:[~2015-07-13 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 18:32 [meta-fsl-demos][PATCH] New packagegroups to organize tools Ann Thornton
2015-07-10 19:21 ` Nikolay Dimitrov
2015-07-10 21:33 ` Ann Thornton
2015-07-13 14:03 ` Nikolay Dimitrov [this message]
2015-07-13 16:17 ` Otavio Salvador
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=55A3C548.3020408@mail.bg \
--to=picmaster@mail.bg \
--cc=Ann.Thornton@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=ra43240@freescale.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.