Thanks for pointing that out! The busybox recipe provided me
insight on how to implement this series in a cleaner way.
I refactor the code and the v2 of the series can be found here:
http://lists.openembedded.org/pipermail/openembedded-core/2019-April/280981.html
Please do not integrate this
Sure, can you integrate this in the while I work on the busybox one? I'll
do it as part of bug 12597 that is also assigned to me
Mariano
On Fri, Apr 5, 2019 at 9:37 AM Burton, Ross wrote:
> Can you also port busybox to this instead of its own hand-coded logic?
>
> Ross
>
> On Fri, 5 Apr 2019
Can you also port busybox to this instead of its own hand-coded logic?
Ross
On Fri, 5 Apr 2019 at 15:27, Mariano Lopez
wrote:
>
> Some binaries are renamed by update-alternatives class at build time
> and some ptest run against a binary belonging to another package. Take
> for example busybox
Some binaries are renamed by update-alternatives class at build time
and some ptest run against a binary belonging to another package. Take
for example busybox or util-linux.
This series adds a directory within the ptest path with symlinks to the
binaries produced by the package, so just adding
