Hello, .... > To that end, I'd like to propose creating a C port of Ruckig, > tentatively called cruckig, maintained as a separate repository. The > upstream Ruckig library is mathematically stable and well-tested at this > point; activity there is mostly wrapper updates, not algorithmic > changes. A C port would be safe to stabilize and maintain independently.
I cannot judge the feasibility of your endeavour but I can tell that you need a better name. Also, I expect that the source tree will diverge quickly from its reference - so why stick to it. How about "cont" - for "continuous", obviously. I also like "screech" (for the sound that the system makes when the library goes wrong, along the idea of what ruckig means). Or just translate it to "scatti". > A few open questions I'd welcome input on: > > 1. Would it make sense to host this under the LinuxCNC organization, > something like https://github.com/LinuxCNC/cruckig? Any would do. But I suggest you start with your personal repository and at some point transfer it to a team maintained one - like that of LinuxCNC. This can be done any time. > 2. On the integration path: should cruckig be bundled inside LinuxCNC > first (similar to how Ruckig is now), go through the Debian packaging > process in parallel, and then be extracted as a proper dependency once > packaged? Or is it cleaner to pursue the separate repo and Debian > package from the start, and only integrate it as a dependency once that > is in place? I suggest to have it as a stable repository somewhere. Debian can then use that as a root of its packaging and LinuxCNC can always have it as a git submodule until it has arrived in the various Linux distros. > 3. I have not personally gone through the Debian packaging process, so > I'd welcome guidance on what that realistically involves and whether the > phased approach is standard practice or just added complexity. It can ship with LinuxCNC as a start and then be extracted. > Looking forward to hearing your thoughts. I had no deeper look at ruckig. So I cannot tell about how difficult it will be. But do not worry about how to integrate it. Since LinuxCNC will need the backports anyway, and will need it faster than Debian has a new package backported, I am confident that it will all be an integration with LinuxCNC first, just like it is now. Best, Steffen _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
