On Tue, 9 Dec 2014 11:27:42 -0800 (PST) "Edward K. Ream" <edream...@gmail.com> wrote:
> Imo, the recent addition of the ckeditor and rope submodules are too > clever by half. > > The following discuss problems with using submodules: > > https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/ > http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ > > There are many problems with using submodules, but imo having to use > git clone --recursive is a show-stopper. There is no indication at > https://github.com/leo-editor/leo-editor that the --recursive > argument is required. > > Furthermore, tracking the "real" ckeditor or rope projects in Leo is > overkill. You could even say it is misguided. Recall that Leo uses > modules in the leo/external folder only if Leo can't otherwise import > those modules. That is, leo/external is a fallback. That being so, > using a relatively static snapshot of code in leo/external should be > perfectly fine--there is no need for up-to-the-minute code. > > So I'd like to do the following: > > 1. Remove the ckeditor and rope submodules. > > 2. "git add" the files in leo/external/ckeditor and > leo/external/rope, possibly removing .git directories if needed. > > The effect would be that git would treat the ckeditor and rope > folders exactly like all others. > > Your comments please. Whenever I've looked in to submodules I've always abandoned there use because of the complexity. I think your path is fine. Cheers -Terry > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
