Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai.kang@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 08/10] os-release: fix install file conflict for multilib
Date: Sat, 29 Sep 2018 13:37:51 +0100	[thread overview]
Message-ID: <b39f86162f18cbaf06d9d2757419255aac9cbec2.camel@linuxfoundation.org> (raw)
In-Reply-To: <7cf91a3e20704f362f975a75775fd864bdb2731c.1538199671.git.kai.kang@windriver.com>

On Sat, 2018-09-29 at 13:43 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
> 
> It fails to create image when install os-release and lib32-os-release 
> both:
> 
> > file /etc/os-release conflicts between attempted installs of
> > os-release-1.0-r0.core2_64 and lib32-os-release-1.0-r0.x86
> 
> The /etc/os-release is a symlink link to ${libdir}/os-release.
> Actually
> the content of files are identical and make /etc/os-release to be
> hard
> link could fix the issue. But according to os-release (5), symlink
> link
> is necessary for initrd environment such as dracut.
> 
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
>  meta/recipes-core/os-release/os-release.bb | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-core/os-release/os-release.bb
> b/meta/recipes-core/os-release/os-release.bb
> index bf4f815a10..4d5487c06d 100644
> --- a/meta/recipes-core/os-release/os-release.bb
> +++ b/meta/recipes-core/os-release/os-release.bb
> @@ -1,10 +1,12 @@
> -inherit allarch
> -
>  SUMMARY = "Operating system identification"
>  DESCRIPTION = "The /usr/lib/os-release file contains operating
> system identification data."
>  LICENSE = "MIT"
>  INHIBIT_DEFAULT_DEPS = "1"
>  
> +inherit allarch multilib_script
> +
> +MULTILIB_SCRIPTS = "${PN}:${sysconfdir}/os-release"

This is exactly the kind of thing I did not want to see
MUTLILIB_SCRIPTS used for. Its now being proposed everywhere you have
an issue with conflicting files without consideration about what
actually makes sense.

What might make more sense here is only to build os-release for the
main namespace and not any of the multilibs. It could RPROVIDE if
necessary.

Cheers,

Richard



  reply	other threads:[~2018-09-29 12:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  5:43 [PATCH v2 00/10] Fix multilib install conflicts kai.kang
2018-09-29  5:43 ` [PATCH 01/10] cups: fix multilib install file conflicts kai.kang
2018-09-29  5:43 ` [PATCH 02/10] bind: " kai.kang
2018-09-29  5:43 ` [PATCH 03/10] man-db: fix multilib install file conflict kai.kang
2018-09-29 12:44   ` Richard Purdie
2018-09-30  1:02     ` Kang Kai
2018-09-29  5:43 ` [PATCH 04/10] groff: fix multilib install file conflicts kai.kang
2018-09-29  5:43 ` [PATCH 05/10] nss: move create blank certificates to pkg_postinst kai.kang
2018-09-29 12:44   ` Richard Purdie
2018-10-02 15:29     ` Kang Kai
2018-10-02 15:53       ` richard.purdie
2018-10-02 16:33         ` Kang Kai
2018-10-11  7:55         ` Kang Kai
2018-09-29  5:43 ` [PATCH 06/10] libcheck: avoid multilib install file conflict kai.kang
2018-09-29 12:42   ` Richard Purdie
2018-09-30  1:03     ` Kang Kai
2018-09-29  5:43 ` [PATCH 07/10] opkg-utils/update-alternatives: not warn same priorities for multilib kai.kang
2018-09-29 12:40   ` Richard Purdie
2018-09-29  5:43 ` [PATCH 08/10] os-release: fix install file conflict " kai.kang
2018-09-29 12:37   ` Richard Purdie [this message]
2018-09-30  1:07     ` Kang Kai
2018-09-29  5:43 ` [PATCH 09/10] gobject-introspection: fix multilib install file conflicts kai.kang
2018-09-29  5:43 ` [PATCH 10/10] vala: update vapigen-wrapper kai.kang
2018-09-29 12:33   ` Richard Purdie
2018-09-30  1:26     ` Kang Kai
  -- strict thread matches above, loose matches on Subject: below --
2018-09-29  5:01 [PATCH 00/10] Fix multilib install conflicts kai.kang
2018-09-29  5:01 ` [PATCH 08/10] os-release: fix install file conflict for multilib kai.kang

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=b39f86162f18cbaf06d9d2757419255aac9cbec2.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kai.kang@windriver.com \
    --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