Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Jacob Kroon" <jacob.kroon@gmail.com>
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] grub-efi-native: use RDEPENDS on grub-native instead of duplicating tools
Date: Fri, 19 Jun 2020 21:35:12 +0200	[thread overview]
Message-ID: <ca209cf1-0c89-634f-ff18-e1049e57034e@gmail.com> (raw)
In-Reply-To: <CACMJ4GZGKQGGoZ=qA1SRvMuesRNDTkOVs4rcm_8xrU=Eur78nA@mail.gmail.com>

On 6/18/20 11:58 PM, Christopher Clark wrote:
> On Thu, Jun 18, 2020 at 1:27 AM Jacob Kroon <jacob.kroon@gmail.com> wrote:
>>
>> On 6/18/20 1:12 AM, Richard Purdie wrote:
>>> On Wed, 2020-06-17 at 16:07 -0700, Christopher Clark wrote:
>>>> Both grub-native and grub-efi-native included packaging for the
>>>> grub-mkimage and grub-editenv tools, which prevented concurrent
>>>> installation of both the grub-native and grub-efi-native packages.
>>>> This caused errors on image generation with wic when populating
>>>> partitions with both legacy and efi boot support, so resolve this by
>>>> removing the duplicated tools from grub-efi-native and add a
>>>> runtime dependency from it to grub-native.> >>
>>>
>>> I think we want to PROVIDES_append_class-native = " grub-efi-native" in
>>> grub and then drop the BBCLASSEXTEND from grub-efi?
>>
>> Just for the record, I tested building grub-native (x86-64) both with
>> platform "pc" and "efi", and in the same build directory, and all tools
>> in ${bindir} were binary identical. Asking in #grub on freenode also
>> confirmed this, apparently Debian packaging also assumes this.
>>
>> So no grub-efi-native required, and we can remove that
>> _class_target/_class_native special handling as well.
> 
> I'm not as confident as I was about the results of the binary
> comparison that I did, since objdump definitely wasn't showing the
> strings differences that were clearly present between those binaries.
> I think that proposing this change was a mistake since there could
> well be other layers that depend on core having separate packages with
> behaviour specific to those that is needed. Sorry for the noise.
> 

I dug some more into this. That GRUB_PKGLIBDIR define which references 
the recipe specific install sysroot is actually unused and could be 
removed. But there are 3 other values that contain the install sysroot 
being encoding in the binaries:

GRUB_DATADIR = 
$TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/usr/share

GRUB_LIBDIR = 
$TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/usr/lib

GRUB_SYSCONFDIR = 
$TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/etc

But all three values refer to directories that are not expected to 
exists at the time they are executed, right ? At least not for me using 
rm_work.bbclass. Where grub-mkimage is used in the efi recipe, -d is 
passed to override the libdir.

So I'd still vote for removing grub-efi-native.

Jacob

  reply	other threads:[~2020-06-19 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 23:07 [PATCH] grub-efi-native: use RDEPENDS on grub-native instead of duplicating tools Christopher Clark
2020-06-17 23:12 ` [OE-core] " Richard Purdie
2020-06-18  8:27   ` Jacob Kroon
2020-06-18 21:58     ` Christopher Clark
2020-06-19 19:35       ` Jacob Kroon [this message]
2020-06-19 23:03         ` Christopher Clark

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=ca209cf1-0c89-634f-ff18-e1049e57034e@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=christopher.w.clark@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox