From: "akuster" <akuster808@gmail.com>
To: Ricardo Salveti <ricardo@foundries.io>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-security][PATCH 1/2] softHSM: add pkg
Date: Tue, 3 Nov 2020 15:27:49 -0800 [thread overview]
Message-ID: <aed5f59d-b222-5961-6949-be25ac355520@gmail.com> (raw)
In-Reply-To: <CAAaKDhEB=gK8gnBiHgBUsnvUtTaP1AP8dRiuVz8-xD2EXCds4A@mail.gmail.com>
On 11/3/20 2:52 PM, Ricardo Salveti wrote:
> Hi,
>
> On Sun, Sep 27, 2020 at 7:16 PM akuster <akuster808@gmail.com> wrote:
>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>> recipes-security/softHSM/softhsm_2.6.1.bb | 30 +++++++++++++++++++++++
>> 1 file changed, 30 insertions(+)
>> create mode 100644 recipes-security/softHSM/softhsm_2.6.1.bb
> Was going over recipes that were duplicated over layers, and this one
> is a newer version of a similar recipe that is already in meta-oe
> (which is a dependency of this layer).
>
> Should we drop the one from meta-oe or should we just update that one
> with the content from this recipe and then remove from meta-security?
No. meta-oe is lower in the stack so I should drop the one in
meta-security and update the one in meta-oe.
I didn't notice the recipe already existed. its all about timing and
effort at this point. we may have time.
thanks for reminding me.
-armin
>
> Thanks,
prev parent reply other threads:[~2020-11-03 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 22:16 [meta-security][PATCH 1/2] softHSM: add pkg akuster
2020-09-27 22:16 ` [meta-security][PATCH 2/2] packagegroup-core-security: add softHSM akuster
2020-11-03 22:52 ` [yocto] [meta-security][PATCH 1/2] softHSM: add pkg Ricardo Salveti
2020-11-03 23:27 ` akuster [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=aed5f59d-b222-5961-6949-be25ac355520@gmail.com \
--to=akuster808@gmail.com \
--cc=ricardo@foundries.io \
--cc=yocto@lists.yoctoproject.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