All of lore.kernel.org
 help / color / mirror / Atom feed
From: <kai.kang@windriver.com>
To: <richard.purdie@linuxfoundation.org>, <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/2] Install rdependent of allarch package with same multilib variant of image
Date: Thu, 26 Jul 2018 00:41:05 +0800	[thread overview]
Message-ID: <20180725164107.8891-1-kai.kang@windriver.com> (raw)

From: Kai Kang <kai.kang@windriver.com>

Hi Richard and Mark,

The series rfc patch is trying to install 64bits packages which is
required by allarch package to 32 bits image. Work for rpm and need
little more work and test for dpkg and opkg.

Take ca-certificates as example. It requires openssl. So it intalls
openssl for both core-image-sato and lib32-core-image-sato. But
lib32-openssl is expected to be installed to lib32-core-image-sato.

So extend rdpendent of allarch package with all multilib variants and
'noarch-' as well.

Extend
ca-certificates -> openssl

to

ca-certificates -> openssl, lib32-openssl, noarch-openssl

Rdepends on openssl and lib32-openssl make both of them exist in
oe-core-repo when do rootfs. And then make both openssl and
lib32-openssl provide noarch-openssl. And only keep noarch-openssl in
RDEPENDS when write package for ca-certificates. When do image rootfs
for lib32-core-image-sato, remove openssl if installed already and
install lib32-openssl to provide noarch-openssl for allarch pacakge
ca-certificates.

And extend rprovides of allarch package with prefix 'noarch-' too that
it may be required by other allarch packages. Put all dependent packages
of all allarch recipes in oe-core to a new ariable 'ALLARCH_RDEP_PKGS'.

Any comment for this method is welcomed. Thanks a lot.

--Kai

Kai Kang (2):
  make allarch packages don't dependent specific multilib package
  WIP: install rdependent packages of allarch packages according to
    image rootfs

 meta/classes/allarch.bbclass         |  3 --
 meta/classes/multilib.bbclass        |  3 +-
 meta/classes/multilib_global.bbclass | 31 ++++++++++++++++-
 meta/classes/nativesdk.bbclass       |  8 +++++
 meta/classes/package_deb.bbclass     |  7 +++-
 meta/classes/package_ipk.bbclass     |  7 +++-
 meta/classes/package_rpm.bbclass     |  8 ++++-
 meta/conf/multilib.conf              | 16 +++++++++
 meta/lib/oe/package_manager.py       | 51 ++++++++++++++++++++++++++--
 meta/lib/oe/rootfs.py                | 28 +++++++++++++++
 10 files changed, 152 insertions(+), 10 deletions(-)

-- 
2.17.1



             reply	other threads:[~2018-07-25 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 16:41 kai.kang [this message]
2018-07-25 16:41 ` [RFC PATCH 1/2] make allarch packages don't dependent specific multilib package kai.kang
2018-07-25 16:41 ` [RFC PATCH 2/2] WIP: install rdependent packages of allarch packages according to image rootfs kai.kang
2018-07-25 22:47 ` [RFC PATCH 0/2] Install rdependent of allarch package with same multilib variant of image richard.purdie
2018-07-26  6:53   ` Kang Kai
2018-07-26  9:07     ` richard.purdie
2018-07-26  9:51       ` Martin Jansa
2018-07-26 11:02       ` Alexander Kanavin
2018-07-26 14:13       ` Mark Hatle

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=20180725164107.8891-1-kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.