From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Dynamic common utilities
Date: Fri, 18 Sep 2015 10:35:45 +0100 [thread overview]
Message-ID: <55FBDAF1.3030906@communistcode.co.uk> (raw)
In-Reply-To: <cover.1442503745.git.alejandro.joya.cruz@intel.com>
On 17/09/15 17:20, Alejandro Joya wrote:
> It provide a virtual reference for the common utilities.
> it replace of the lock to busybox, it will be simple exchange between other
> common utilities like gnu core utils or toybox among others.
>
> In order to enable its required to fill at the distro conf or local.conf
>
> VIRTUAL-RUNTIME_login_manager ?= "busybox"
> PREFERRED_PROVIDER_virtual/anybox ?= "busybox"
> PREFERRED_RPROVIDER_virtual/anybox ?= "busybox"
> VIRTUAL-RUNTIME_anybox ?= "busybox"
> VIRTUAL-RUNTIME_anybox-hwclock ?= "busybox-hwclock"
>
> The following changes since commit f0189829498e30231d826c9f55aad73e622d076e:
>
> qemu: Update to upstream patches (2015-09-14 11:22:02 +0100)
>
> are available in the git repository at:
>
> git://github.com/Ajoyacr/openembedded-core anybox
> https://github.com/Ajoyacr/openembedded-core/tree/anybox
>
> Alejandro Joya (3):
> core-mage-minimal-initramfs: overwrite hardcoded dependency to virtual
> reference
> initramfs-framework: overwrite hardcoded dependency to virtual
> reference
> packagegroup-core-boot: overwrite hardcoded dependency to virtual
> reference
>
> meta/recipes-core/images/core-image-minimal-initramfs.bb | 2 +-
> meta/recipes-core/initrdscripts/initramfs-framework_1.0.bb | 2 +-
> meta/recipes-core/packagegroups/packagegroup-core-boot.bb | 6 +++---
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
is 'anybox' a good name for the virtual provider? What happens if we have a new
suite of core utility replacements without box in the name, I assume it will be
a nightmare to retroactivly change the name so we should probably come up with a
more generic one now. virtual/core-utils, virtual/base-utils?
Cheers,
Jack.
next prev parent reply other threads:[~2015-09-18 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 16:20 [PATCH 0/3] Dynamic common utilities Alejandro Joya
2015-09-17 16:20 ` [PATCH 1/3] core-mage-minimal-initramfs: overwrite hardcoded dependency to virtual reference Alejandro Joya
2015-09-17 16:20 ` [PATCH 2/3] initramfs-framework: " Alejandro Joya
2015-09-17 16:20 ` [PATCH 3/3] packagegroup-core-boot: " Alejandro Joya
2015-09-18 9:35 ` Jack Mitchell [this message]
2015-09-18 15:19 ` [PATCH 0/3] Dynamic common utilities Khem Raj
2015-09-18 15:44 ` Mark Hatle
2015-09-18 17:43 ` 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=55FBDAF1.3030906@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.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