________________________________ From: Sebastian Kuzminsky <[email protected]>
>I have experience with git submodules, and I am very much not a fan. >submodules are occasionally useful, but it's a suboptimal solution. My >main objection is that they introduce additional complexity into the >project's revision control system, which is already a barrier to entry >for some developers. >I'd prefer to find a non-submodules way to make qtvcp/qtscreen work well >with linuxcnc, be easy for developers to work on, and be easy for users >to get their hands on. Excellent I was hoping someone did have some experience I did read that submodules are a pain, most articles recommended git subtree https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree https://developer.atlassian.com/blog/2015/05/the-power-of-git-subtree/ It seems to indicate that it's simpler: git subtree does not require users of your repository to learn anything new. They can ignore the fact that you are using git subtree to manage dependencies. I'm not sure if this changes your mind or not. >I don't mind incorporating that history into linuxcnc, if it's >reasonably confined to the new UI/feature and it doesn't break the build >(for when we have to bisect history later). >Does it add new build dependencies? Runtime dependencies? >I'd be happy to help incorporate it into our packaging system. I can't see how it would break the building of linuxcnc. There are no build time dependency changes. There are runtime dependencies that I have not added to the Debian list - I may need some help there - it's been awhile. I asked this question just because the opportunity is easy now if we wished to keep it separate. It's of course easiest for me if I leave it as it is. I just wondered if it would be better to have linuxcnc broken up a bit and a new VCP would be a start. Thanks Chris M ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
