[Debian-lego-team] NQC packaging and upstream change

[Matthew Sheets]

Hello Nicolas,

> What is the license of the files under emscripten directory,
> are they also covered by the MPL?

Yes, the maehw/WebNQC project was itself a fork of BrickBot/NQC, and it continued under the MPL in that fork.  Its focus was on building NQC for WebAssembly and dropped support for the existing build targets, but I liked the concept and worked to incorporate the WebAssembly support from that project back into this BrickBot/NQC project while also preserving support for NQC's existing build targets.

> I notice that there is no way to run the install target without building
> the emscripten version of NQC.

The "all" dependency on the "install" target appears to be a leftover from the original import.  I don't use install that way myself, either, and have no issue with removing the "all" dependency from the "install" target if that would work for folks here.

> Would you consider making a release?

If all looks stable after we get the install target straightened out, I would certainly be willing do so.  One thing I haven't been sure of is how to appropriately version a release that is picking up where a dormant upstream left off.  A version 4.0 would clearly and distinctly delineate the point of the project transition, while a version 3.2 might be closer to what semantic versioning practices would dictate based on functional changes.  I don't think a reset to 1.0 would fit here, either from a project standpoint or a packaging standpoint.  (I can say, though, that I am not planning to continue the "-r" suffix scheme.)  I'm currently leaning towards a 4.0 for delineation clarity but would welcome any thoughts.


Thank you,
Matthew