On Tuesday 9. November 2010 09.42.18 Volker Krause wrote: > But I still know very little about git myself. Marc suggested it might be > possible with the use of something like git submodules to come up with a > hybrid solution which combines the best of both worlds, allowing > individually and combined checkout/build.
Submodules are not really meant for the idea of developing in the various different sub-modules, they are more meant to 'tag'. For example if want to release all kde modules you can go into each repo and make a tag there, or you can store the release-sha1 of each of those sub-repos in an external repo. This concept is more in line with what submodules in git represent. Practically speaking this means that you still need to go into each library git module and do a git pull both when you did the initial checkout, and again for each time you want to update your 'libs'. For completeness sake I'll mention the alternative, though from a social standpoint I'm not sure its feasable in KDE; Alternatively you make everyone that develops on any of these repos update the meta repo. Which means that at each and every push in any of the subrepos you also commit and push the meta repo. Thinking about this; maybe the sysadmins can research if they can make this happen automatically... disclaimer; I'm no submodules expert and my limited experience is from 2 versions ago. Also I'm known to make mistakes. -- Thomas Zander _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest