Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	California Sullivan <california.l.sullivan@intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] initramfs-framework: split setup-live and install-efi into separate recipes
Date: Mon, 04 Sep 2017 08:35:56 +0200	[thread overview]
Message-ID: <1504506956.12799.55.camel@intel.com> (raw)
In-Reply-To: <CAP9ODKpRT_BQGqzCd-fihZp-Dy4w0uiNr2bG_AYAvdta4wQPRg@mail.gmail.com>

On Sat, 2017-09-02 at 15:17 -0300, Otavio Salvador wrote:
> On Fri, Sep 1, 2017 at 9:04 PM, California Sullivan
> <california.l.sullivan@intel.com> wrote:
> > Having these the initramfs-framework recipe
> > forced initramfs-framework
> > users to build several tools they didn't need, and made it more
> > difficult to declare the recipe as allarch.
> > 
> > Fixes [YOCTO #12024].
> > 
> > Signed-off-by: California Sullivan <california.l.sullivan@intel.com
> > >
> 
> The patch should be based on the allarch patch I sent as it adds the
> dependencies on the whitelist. So you can also set them as allarch.

I would prefer to keep initramfs-framework-setup-live/install-efi as
arch-specific and only make initramfs-framework itself allarch. It's
just a gut feeling about the (minor) advantage of not having to rebuild
these two small recipes vs. the additional complexity of the layer.conf
and having to keep that up-to-date.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.




  reply	other threads:[~2017-09-04  6:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02  0:04 [PATCH] initramfs-framework: split setup-live and install-efi into separate recipes California Sullivan
2017-09-02 18:17 ` Otavio Salvador
2017-09-04  6:35   ` Patrick Ohly [this message]
2017-09-04 12:46     ` Otavio Salvador
2017-09-04 13:07       ` Patrick Ohly
2017-09-04 13:25         ` 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=1504506956.12799.55.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=california.l.sullivan@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    /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