On Tue, May 26, 2020 at 10:11 AM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > On Mon, May 25, 2020 at 8:41 PM Takashi Yamamoto > <yamam...@midokura.com.invalid> wrote: > > > On Tue, May 26, 2020 at 12:48 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > We should all be using a consistent, common version of > > > kconfig-frontends. A snapshot was taken and has never disappeared from > > > internet contrary to other statements it is always been here and will > > > always be here: https://bitbucket.org/nuttx/tools/src/master/ > > > > > > We do not accept any Python-based tools in the critical build path. > > > There are some secondary Python scripts under tools/ but we cannot > > > permit the introduction of any new user tool requirements in the basic > > > build. That is simply off-limits. > > > > > > Think of the NuttX user first! Technologies and tools are much further > > > down the list. > > > > i can understand you don't like to have python dependency. > > but i don't think the "user first" argument is not a good reason. > > for some users (like me) python is definitely easier to deal with > > than the current state of kconfig-frontends. > > > What don't you like about the current state of kconfig-frontends?
having to build and install a tool from source is already cumbersome. especially when you need to apply patches manually. it isn't a problem for me anymore because i already get used to it. but i guess it's a hurdle for new users. > > Nathan
