Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <bisson.gary@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] mfgtools: bump revision to latest uuu version
Date: Wed, 12 Jun 2019 18:41:02 +0200	[thread overview]
Message-ID: <20190612164102.GA6917@t450s.lan> (raw)
In-Reply-To: <20190612155844.GC2647@scaer>

Hi Yann,

On Wed, Jun 12, 2019 at 05:58:44PM +0200, Yann E. MORIN wrote:
> Arnout, Gary, All,
> 
> On 2019-06-11 11:52 +0200, Arnout Vandecappelle spake thusly:
> > On 11/06/2019 10:15, Gary Bisson wrote:
> > >>  So, I'm in favour of creating BR2_PACKAGE_HOST_UUU and killing
> > >> BR2_PACKAGE_HOST_MFGTOOLS.
> > >>
> > >>  I marked the patch as Not Applicable in patchwork. If you convince me to do it
> > >> this way after all, we can fish it up again.
> > > 
> > > Ok I can do that. I'll offer another series that deprecates mfgtools and creates
> > > a new uuu package.
> > 
> >  Maybe first Peter and Thomas can confirm that this is the right approach?
> > 
> >  In summary: the current version of mfgtools creates a completely different
> > program called uuu that is used in a completely different way. In other words,
> > existing scripts will no longer work. Because of this, my proposal is to create
> > a new package for it, and move the existing mfgtools to legacy.
> 
> 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
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]
4- the code is ugly (Windows tool ported to Linux at some point)
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.

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

  reply	other threads:[~2019-06-12 16:41 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 [this message]
2019-06-12 17:05           ` Yann E. MORIN
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=20190612164102.GA6917@t450s.lan \
    --to=bisson.gary@gmail.com \
    --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