From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?J=F6rg?= Krause Date: Thu, 02 May 2019 11:33:17 +0200 Subject: [Buildroot] [PATCH 2/2] package/mfgtools: bump to version 1.2.91 In-Reply-To: <4bf9c494-f6dc-e1a8-abad-3d87cbf1e051@mind.be> References: <20190430201121.15634-1-joerg.krause@embedded.rocks> <20190430201121.15634-2-joerg.krause@embedded.rocks> <880fdc14-d19f-020b-9735-9e0077e6be76@mind.be> <7552b9cbd58edcd667f52531ed75e3fe57cd705c.camel@embedded.rocks> <4bf9c494-f6dc-e1a8-abad-3d87cbf1e051@mind.be> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Thu, 2019-05-02 at 09:52 +0200, Arnout Vandecappelle wrote: > > On 02/05/2019 08:51, J?rg Krause wrote: > > > > The > > > > problem is, that git provides the version information of Buildroot. > > > Is it that much of a problem if the Buildroot version is used? > > mfgtools saves the version string in generated runtime scripts. So this > > is a problem. > > Yes, I understand that. But the effect is that `uuu --version` will print > 2019.02 instead of 1.2.91, right? So my question is: is it that much of a > problem that this happens? mfgtools checks its version information with a version string saved in user provided command list files. If the version string of the file is newer than the version of mfgtools it will abort. So, yes, it is a problem. > I'm asking because I'm sure there are other packages that have that behaviour. > Are we going to try to find and fix all of them? Or just live with the fact that > some packages report the wrong version? There are! The issue with such packages is when filing a bug report for upstream, the maintainer might wonder about the strange version information. Best regards J?rg Krause