Because unlike other commands, getlimits is a noinst_PROGRAM. It's expected to be used by its tests only. I checked Ubuntu, Debian and Fedora, none of them provides getlimits. So if not for the ptest packages, we would not be using this command either.
Regards, Qi -----Original Message----- From: Ross Burton <ross.bur...@arm.com> Sent: Friday, June 7, 2024 9:34 PM To: Chen, Qi <qi.c...@windriver.com> Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core][PATCH 1/2] coreutils: split out coreutils-getlimits On 6 Jun 2024, at 13:20, Chen Qi via lists.openembedded.org <Qi.Chen=windriver....@lists.openembedded.org> wrote: > > From: Chen Qi <qi.c...@windriver.com> > > Previously, the noinst_PROGRAM getlimits is put in coreutils-ptest > package in order to execute the ptest. However, this command might > also be needed by other ptest packages. As an example, findutils > 4.10.0 ptest pacakge would need this command. So we split it out into > a new package. Why would we not just put this in the main coreutils package? What’s so special about getlimits that it needs a standalone package? Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#200443): https://lists.openembedded.org/g/openembedded-core/message/200443 Mute This Topic: https://lists.openembedded.org/mt/106521746/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
