On 3/9/2020 3:33 PM, Gregory Nutt wrote:
I understand that there have been exceptions made for Apache
projects to
allow GPL support tools into Apache project. I would not have any
difficulty granting those repositories to the project. But I cannot
comfortably use the github NuttX repository.
The GPL projects no longer exist. I keep snapshots because they are
necessary to NuttX and are not generally available elsewhere (without
a bit of Googling): e.g. kcoinfig-frontends. I also have some
snapshots of old GPL tools that runs with NuttX; newer versions
probably do not: Eg., genromfs. There are other necessary tarballs
there just to support on-stop-shopping: E.g., gperf
There are also custom implementations for NuttX that leverage GPL
code but for which there is no upstream project like the NuttX host
nxfuse implementation.
And all of the buildtest files are there.
No, there is nothing that can be moved upstream.
There are also binaries for loading into WiFi chips there. You cannot
use the WiFi chips with the firmware binaries. There are not GPL and
can be free distributed. But they are not BSD or Apache either.
Everything is critical for building NuttX and supporting NuttX
configurations and testing. Nothing can be in an open repository.
Nothing can go upstream. Nothing can go to the Apache repositories
(without some special dispensation).
That is just the tools repository. There is also a uClibc++ port to
NuttX that would never be accepted upstream and the buildroot repository
for building NuttX toolchains. This derives from the original
buildroot, hacked down to the bare bones, and make to build NuttX
toolchains. Is not compatible with upstream buildroot (or even
marginally related to it).
These also must be protected.
There is also a port the LLVM libc++ somewhere. I don't recall where.
That was done by Alan and is a critical piece of a NuttX solution for
C++11 support. I don't think that this is a candidate for upstreaming
either, at least not in its current form.
