On 11/20/2018 04:52 PM, Alexey Brodkin wrote: > Hi Otavio, > >> -----Original Message----- >> From: Otavio Salvador [mailto:otavio.salvador at ossystems.com.br] >> Sent: Tuesday, November 20, 2018 6:49 PM >> To: Burton, Ross <ross.burton at intel.com> >> Cc: Peter Kjellerstedt <peter.kjellerstedt at axis.com>; Marek Vasut <marex at denx.de>; Tom Rini <trini at konsulko.com>; Otavio >> Salvador <otavio at ossystems.com.br>; Alexey Brodkin <alexey.brodkin at synopsys.com>; Patches and discussions about the oe-core >> layer <openembedded-core at lists.openembedded.org>; linux-snps-arc at 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.burton at 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. You can use mkenvimage on target, I had to do that a few times. -- Best regards, Marek Vasut
