From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Subject: Re: dtc/u-boot tool naming, "ftdump", "mkimage" Date: Wed, 14 Jan 2009 14:11:22 -0500 Message-ID: <496E38DA.8080408@ge.com> References: <496E2796.3090405@genesi-usa.com> <20090114181028.GB7768@yoda.jdub.homelinux.org> <496E3604.8030007@genesi-usa.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <496E3604.8030007@genesi-usa.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: u-boot-bounces@lists.denx.de Errors-To: u-boot-bounces@lists.denx.de To: Matt Sealey Cc: u-boot@lists.denx.de, Josh Boyer , devicetree-discuss@ozlabs.org List-Id: devicetree@vger.kernel.org Hi Matt, Matt Sealey wrote: > Josh Boyer wrote: >> On Wed, Jan 14, 2009 at 11:57:42AM -0600, Matt Sealey wrote: >>> I just noticed (was told by an affiliate) that the DTC compiler tools >>> shares a tool name "ftdump" with the Freetype project. I was doing a >>> lazy packaging effort to get a few tools around so we can all be running >>> the same version and build some custom kernel RPMs, and this came up. >>> >>> Wouldn't a better name be "fdtdump", do you think? It's usually not a >>> fun idea to conflict with tools already on the system. A user may run >>> "ftdump" and get the Freetype tool because of a simple mistake in paths >>> or so. >>> >>> With regards to U-Boot proper, I would say the same is true of "mkimage" >>> which conflicts with jigdo. In essence, while U-Boot is usually >>> installed into a user's home directory (~/bin etc.) simple path mixups, >>> going to root shell, using another box etc. means you may have multiple >>> same-named tools on a system for various work, which do different things. Mkimage and ftdump are different audiences (OK, the same people but the chairs are arranged differently ;-). [snip] IMHO, the ftdump issue needs to be addressed at the DTC level (Jon Loeliger and David Gibson). U-Boot (and the linux kernel) is being driven by DTC. I won't address mkimage since I don't have a dog in that fight. [snip] > -- Matt Best regards, gvb From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Wed, 14 Jan 2009 14:11:22 -0500 Subject: [U-Boot] dtc/u-boot tool naming, "ftdump", "mkimage" In-Reply-To: <496E3604.8030007@genesi-usa.com> References: <496E2796.3090405@genesi-usa.com> <20090114181028.GB7768@yoda.jdub.homelinux.org> <496E3604.8030007@genesi-usa.com> Message-ID: <496E38DA.8080408@ge.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Matt, Matt Sealey wrote: > Josh Boyer wrote: >> On Wed, Jan 14, 2009 at 11:57:42AM -0600, Matt Sealey wrote: >>> I just noticed (was told by an affiliate) that the DTC compiler tools >>> shares a tool name "ftdump" with the Freetype project. I was doing a >>> lazy packaging effort to get a few tools around so we can all be running >>> the same version and build some custom kernel RPMs, and this came up. >>> >>> Wouldn't a better name be "fdtdump", do you think? It's usually not a >>> fun idea to conflict with tools already on the system. A user may run >>> "ftdump" and get the Freetype tool because of a simple mistake in paths >>> or so. >>> >>> With regards to U-Boot proper, I would say the same is true of "mkimage" >>> which conflicts with jigdo. In essence, while U-Boot is usually >>> installed into a user's home directory (~/bin etc.) simple path mixups, >>> going to root shell, using another box etc. means you may have multiple >>> same-named tools on a system for various work, which do different things. Mkimage and ftdump are different audiences (OK, the same people but the chairs are arranged differently ;-). [snip] IMHO, the ftdump issue needs to be addressed at the DTC level (Jon Loeliger and David Gibson). U-Boot (and the linux kernel) is being driven by DTC. I won't address mkimage since I don't have a dog in that fight. [snip] > -- Matt Best regards, gvb