Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: richard.purdie@linuxfoundation.org, alex.kanavin@gmail.com,
	leimaohui@fujitsu.com
Cc: Denys Dmytriyenko <denis@denix.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] gzip: upgrade 1.13 -> 1.14
Date: Tue, 22 Apr 2025 15:51:21 -0700	[thread overview]
Message-ID: <8f5a866f-e11d-4619-b159-8d3db541af52@gmail.com> (raw)
In-Reply-To: <41b65472c37b399e2d4c770819bf7868cd145665.camel@linuxfoundation.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1508 bytes --]

On 4/22/25 8:36 AM, Richard Purdie via lists.openembedded.org wrote:
> On Tue, 2025-04-22 at 17:24 +0200, Alexander Kanavin via
> lists.openembedded.org wrote:
>> On Thu, 17 Apr 2025 at 12:21, leimaohui via lists.openembedded.org
>> <leimaohui=fujitsu.com@lists.openembedded.org> wrote:
>>> +Subject: [PATCH] tests/reference: fix invalid option of od issue
>>> +
>>> +ptest issue:
>>> +| od: invalid option -- 'A'
>>> +| BusyBox v1.37.0 () multi-call binary.
>>
>> Instead of working around busybox od limitations with a patch, ptest
>> package should rdepend on coreutils to pull in the real original od.
> 
> Agreed, I've been meaning to reply to say exactly this!
> 

Consider other side of this as well.
Many embedded systems do use busybox heavily, imposing dependencies for 
tests like this would mean ptests are less relevant for such usecases 
since bringing coreutils might also shunt other busybox utilities along 
the way.

I would ask this patch to be proposed to gzip upstream first though.

> Cheers,
> 
> Richard
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#215233): https://lists.openembedded.org/g/openembedded-core/message/215233
> Mute This Topic: https://lists.openembedded.org/mt/112310990/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2613 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  reply	other threads:[~2025-04-22 22:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 10:21 [OE-core] [PATCH] gzip: upgrade 1.13 -> 1.14 Lei Maohui
2025-04-22 15:24 ` Alexander Kanavin
2025-04-22 15:36   ` Richard Purdie
2025-04-22 22:51     ` Khem Raj [this message]
2025-04-22 23:40       ` Alexander Kanavin
2025-04-23  0:30         ` Khem Raj
2025-04-23  3:53   ` 回复: " Yiding Liu (Fujitsu)
2025-04-24 10:43     ` Richard Purdie
2025-04-27  8:12       ` Yiding Liu (Fujitsu)

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=8f5a866f-e11d-4619-b159-8d3db541af52@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=denis@denix.org \
    --cc=leimaohui@fujitsu.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