On Thu, 2011-06-23 at 10:40 +0100, Phil Blundell wrote: > On Thu, 2011-06-23 at 12:08 +0800, Xu, Dongxiao wrote: > > > -----Original Message----- > > > From: openembedded-core-boun...@lists.openembedded.org > > > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > > > Phil Blundell > > > Sent: Wednesday, June 22, 2011 7:45 PM > > > To: Patches and discussions about the oe-core layer > > > Subject: Re: [OE-core] [PATCH 1/1] libc-locale: split locale handling > > > from libc > > > recipe. > > > > > > I still don't quite understand why the virtual/libiconv provider has > > > moved from > > > eglibc to eglibc-locale. Can you explain what's going on there? > > > > Generally, the purpose of this patch is to reduce eglibc's do_package time. > > > > Since many other recipes' do_package have dependency on eglibc's > > do_package, thus the sooner eglibc could finish its do_package, the ealier > > can other do_packages be executed, which improves the parallelism. > > > > From our study, we found most of eglibc's do_package time is used to handle > > locale. Therefore we split all the locale related stuffs into a separately > > recipe eglibc-locale. > > Yes, I understand that. But I don't think this answers the question > about why, specifically, glibc-locale is now PROVIDEing > virtual/libiconv. Does that recipe, in fact, implement libiconv?
I must admit I was wondering about this too. Isn't the libiconv functionality still packaged as part of the libc recipe, not the locale part? Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
