Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] mfgtools: bump revision to latest uuu version
Date: Wed, 12 Jun 2019 19:05:06 +0200	[thread overview]
Message-ID: <20190612170506.GF2647@scaer> (raw)
In-Reply-To: <20190612164102.GA6917@t450s.lan>

Gary, All,

On 2019-06-12 18:41 +0200, Gary Bisson spake thusly:
> On Wed, Jun 12, 2019 at 05:58:44PM +0200, Yann E. MORIN wrote:
[--SNIP--]
> > Why ditch the older one? People are almost certain to have scripts that
> > rely on it, and since the new one is not a drop-in replacement, we can
> > keep the old one.
> 
> Reasons behind that change were:
> 1- the current code keeps having build issues

14 build failures since it was introduced 1.5 years ago, that's not
really breaking all over the place either. ;-) Besides, it really
started to break in May this year, and they all happen on Xogium's
autobuilder. Bisecting should be relatively easy, there are only about
29 commits between 2019.05-rc1 (where it seems it was still working) and
1cbc8172 (the first known failure).

> 2- the upstream project doesn't accept any patch anymore [1]
> 3- all NXP releases now use this new version, it doesn't provide scripts
>    for the old tool any longer, even for imx6/7 releases [2]

Well, I'm not speaking about the upstream tools, but tools that people
will have written for their own use, which we may never have heard of.
If they use it, it works for them, so why remove it?

> 4- the code is ugly (Windows tool ported to Linux at some point)

When has upstream code quality been a concern for us? ;-)

> 5- this tool is pretty much useless without imx-uuc, right now imx-uuc
>    is working with both, but nothing is for sure about future uuc
>    releases.

Ah, that is indeed a good reason to drop it: if the imx-uuc, which we
ship for the target, needs to go hand-in-hand with mfgtools/uuu, then it
makes sense to even completely drop mfgtools.

This is actually the only reason that I find valid, and it is a
compeling reason.

So yes: rename the package to imx-uuu, and completely drop mfgtools.

Thanks for the detailed explanations!

Regards,
Yann E. MORIN.

> But if you feel strongly about maintaining that package on our own in BR
> let me know.
> 
> Regards,
> Gary
> 
> [1] https://github.com/NXPmicro/mfgtools/pull/104
> [2] https://www.nxp.com/webapp/Download?colCode=imx-yocto-L4.14.98_2.0.0_ga

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-06-12 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 10:53 [Buildroot] [PATCH v3] mfgtools: bump revision to latest uuu version Gary Bisson
2019-06-08 20:28 ` Arnout Vandecappelle
2019-06-11  8:15   ` Gary Bisson
2019-06-11  9:52     ` Arnout Vandecappelle
2019-06-11 11:07       ` Thomas Petazzoni
2019-06-12 15:58       ` Yann E. MORIN
2019-06-12 16:41         ` Gary Bisson
2019-06-12 17:05           ` Yann E. MORIN [this message]
2019-06-08 20:28 ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190612170506.GF2647@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox