Bitbake recipe for uutils-coreutils

Bitbake recipe for uutils-coreutils

[ecordonnier]

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

Hello,
I am writing a bitbake recipe for uutils-coreutils, which is a rewrite in
rust of GNU coreutils ( https://github.com/uutils/coreutils ). This project
uses an MIT license.

I want to upstream this recipe, however I am not sure whether poky or
meta-openembedded would be the better option. Currently, uutils-coreutils
is still in development, and does not yet provide stty. Also, some
test-cases from the GNU coreutils test-suite are still failing, but it is
already in a "working" state.

In order to replace coreutils in the poky image, I used the "PROVIDE"
mechanism in the uutils-coreutils recipe:
PROVIDES = "coreutils"
RPROVIDES:${PN} = "coreutils"

What do you recommend? Sending patches to meta-openembedded or rather to
poky / poky-contrib?

Thanks,
Etienne Cordonnier

[-- Attachment #2: Type: text/html, Size: 964 bytes --]

Re: [poky] Bitbake recipe for uutils-coreutils

[Khem Raj]

On Wed, Jul 20, 2022 at 12:24 PM Etienne Cordonnier via
lists.yoctoproject.org
<ecordonnier=snapchat.com@lists.yoctoproject.org> wrote:
>
> Hello,
> I am writing a bitbake recipe for uutils-coreutils, which is a rewrite in rust of GNU coreutils ( https://github.com/uutils/coreutils ). This project uses an MIT license.
>
> I want to upstream this recipe, however I am not sure whether poky or meta-openembedded would be the better option. Currently, uutils-coreutils is still in development, and does not yet provide stty. Also, some test-cases from the GNU coreutils test-suite are still failing, but it is already in a "working" state.
>
> In order to replace coreutils in the poky image, I used the "PROVIDE" mechanism in the uutils-coreutils recipe:
> PROVIDES = "coreutils"
> RPROVIDES:${PN} = "coreutils"
>
> What do you recommend? Sending patches to meta-openembedded or rather to poky / poky-contrib?

Perhaps meta-oe might be a good place to house it and it can graduate
from there to core in due course if need arises.

>
> Thanks,
> Etienne Cordonnier
>
> 
>