On Sat, May 2, 2020 at 5:09 PM Brennan Ashton <bash...@brennanashton.com> wrote:
> We certainly can look at what to do about the kconfig-frontend code. Some > distributions package it up, there is no brew install for it :/ it is GPL > code if I remember correctly so officially bringing it under the project > might be hard. I can look at if outside of the project we could maintain a > tap for it which would provide easier onboarding. I think that is the only > tool that we rely for all builds that is usually built from source. gperf > uboot-tools are fairly easy to get via other sources. I think it was said early on that under some circumstances, the ASF may allow to host a mirror for code of "well-known" GPL'd tools if they are important to a project. Indeed I think kconfig is a very important development tool and also well-known as a number of well-known projects use it. The port we use disappeared from the Internet some months ago, but luckily before that happened Greg had the foresight to mirror it in his bit bucket "tools" repository. This tool is pretty important to NuttX, so I think we should figure out a way to host a copy of the sources. I don't consider this as a fork or (worse) a hostile fork, especially since we aren't trying to compete with another kconfig project; rather, we're just trying to ensure the longevity of a tool that we (and other significant projects) depend on, as things come and go on the internet over time. Nathan
