Not quite. What Khem was aiming for was to modify the packaging of coreutils so that individual binaries end up in their own packages. Currently this is not done for any of the coreutil binaries, but if you look at, e.g., util-linux, you will see this setup for quite a number of its utils.
However, a simpler solution would probably be to just enable comm in busybox… //Peter From: [email protected] [mailto:[email protected]] On Behalf Of yahia farghaly Sent: den 9 september 2017 18:06 To: Khem Raj <[email protected]> Cc: Patches and discussions about the oe-core layer <[email protected]> Subject: Re: [OE-core] [meta-oe][PATCH] gnupg: added a coreutils runtime dependancy to gnupg recipe sorry if my question is naive, this is my first time working with yocto and the first patch i submit in an open source project On 9 September 2017 at 03:51, yahia farghaly <[email protected]<mailto:[email protected]>> wrote: Ok, this is a nice idea what i think is i may take only comm.c and its depends then compiling it and try to produce package. is this idea good ? Mr.Chen Qi, what do you think about making a specific package for 'comm' which is a part of coreutils ? On 9 September 2017 at 01:07, Khem Raj <[email protected]<mailto:[email protected]>> wrote: On Fri, Sep 8, 2017 at 3:17 PM, Yahia Farghaly <[email protected]<mailto:[email protected]>> wrote: > From: yahiafarghaly <[email protected]<mailto:[email protected]>> > > When using 'apt-key add' on the target image, the gnupg is required > but for gnupg to be fully functional, the coreutils is required to be exist > with the gnupg. > Otherwise, it may throw an error in runtime as one of components of coreutils > is missing. > For 'apt-key add', i faced the error of 'comm: command not found' so as > proper solution, i submit this change. > > Signed-off-by: yahiafarghaly > <[email protected]<mailto:[email protected]>> > --- > meta/recipes-support/gnupg/gnupg_2.2.0.bb<http://gnupg_2.2.0.bb> | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/meta/recipes-support/gnupg/gnupg_2.2.0.bb<http://gnupg_2.2.0.bb> > b/meta/recipes-support/gnupg/gnupg_2.2.0.bb<http://gnupg_2.2.0.bb> > index 0176ddd..8aa0951 100644 > --- a/meta/recipes-support/gnupg/gnupg_2.2.0.bb<http://gnupg_2.2.0.bb> > +++ b/meta/recipes-support/gnupg/gnupg_2.2.0.bb<http://gnupg_2.2.0.bb> > @@ -44,3 +44,5 @@ do_install_append() { > PACKAGECONFIG ??= "gnutls" > PACKAGECONFIG[gnutls] = "--enable-gnutls, --disable-gnutls, gnutls" > PACKAGECONFIG[sqlite3] = "--enable-sqlite, --disable-sqlite, sqlite3" > + > +RDEPENDS_${PN} = "coreutils" can we make the packaging more granular where comm is packages into a package of its own e.g. coreutils-comm and then create specific rdep on coreutils-comm > -- > 2.7.4 > > -- > _______________________________________________ > Openembedded-core mailing list > [email protected]<mailto:[email protected]> > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin<https://linkedin.com/in/yahiafarghaly> - GitHub<https://github.com/yahiafarghaly> -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin<https://linkedin.com/in/yahiafarghaly> - GitHub<https://github.com/yahiafarghaly>
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
