Hi Otavio, > -----Original Message----- > From: Otavio Salvador [mailto:otavio.salva...@ossystems.com.br] > Sent: Tuesday, November 20, 2018 6:49 PM > To: Burton, Ross <ross.bur...@intel.com> > Cc: Peter Kjellerstedt <peter.kjellerst...@axis.com>; Marek Vasut > <ma...@denx.de>; Tom Rini <tr...@konsulko.com>; Otavio > Salvador <ota...@ossystems.com.br>; Alexey Brodkin > <alexey.brod...@synopsys.com>; Patches and discussions about the oe-core > layer <openembedded-c...@lists.openembedded.org>; > linux-snps-arc@lists.infradead.org > Subject: Re: [OE-core] [PATCH v3] u-boot: Add mkenvimage tool > > On Tue, Nov 20, 2018 at 1:40 PM Burton, Ross <ross.bur...@intel.com> wrote: > > > > (hit sent too early) > > > > Of course how big are these tools, and is it really useful splitting > > them up? If we're talking a 10k binary, is putting them in separate > > packages worth the complication? > > I think it makes sense to split; we are building an embedded system > build system and granular installation is a must have. Using PN to > install all tools is a win win combination.
Please note we're discussing _host_ tools here! So do we really care if there's one more utility installed on development host? And if someone installs those U-Boot host utilities on the target then most probably this target is not super embedded any longer. -Alexey _______________________________________________ linux-snps-arc mailing list linux-snps-arc@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-snps-arc
