On Mon, May 25, 2020 at 12:28 PM Gregory Nutt <spudan...@gmail.com> wrote: > Most projects that use kconfig-frontends use a snapshot version that is > built into the codebase. We cannot do that because kconfig-frontends is > GPL. However, I still argue that we should use a fixed, common version > of kconfig-frontends... no matter what is available in some bleeding > edge repository. > > That is important because if new and/or incompatible features are added > to the bleeding edge kconfig-frontends then are exploited in NuttX, this > will cause problems for the rest of the world who do not have those > features. That is best solved by everyone using a common version of > kconfig-frontends, that being the one at > https://bitbucket.org/nuttx/tools/src/master/ > > If, for some reason, we want to have some features that are available > only in some newer release, then we should carefully integrate a new > snapshot at https://bitbucket.org/nuttx/tools/src/master/, make an > announcement to all NuttX users indicating our intent to upgrade to a > new version, and after some time then, and only then. we can exploit any > new features. Any willy-nilly uncontrolled use of kconfig-frontends > versions will not have a good result. It will break user's builds! We > need to be be careful, measured, and slow when considering any updates > to this tool.
I agree, and all the more reason we should ensure that our project has a controlled snapshot of this tool -- and to ensure the longevity of that snapshot so that it will not be lost suddenly! Nathan
