https://bugs.kde.org/show_bug.cgi?id=362687
--- Comment #1 from Michael Pyne <mp...@kde.org> --- Is this for Qt5? Reason I ask is that I can imagine good reasons why someone would not want to have git automatically pull down every possible Qt5 submodule just because someone was innocently meaning to get qtbase. So assuming we go with making it an option, the way I would probably implement this would be to refactor the existing Updater::Git module (in modules/ksb/Updater/Git.pm) to allow for customization of clones and updates, make a subclass of Updater::Git that uses the customization to actually conduct a submodule-aware clone/update/etc., and then have an option for the module that causes kdesrc-build to create the new subclass instead of Updater::Git when creating the scmType for the module (probably in ModuleSet.pm's _initializeNewModule). This does leave open the difficulty that this would only work with non-"KDE Project" modules (which are already a separate subclass) but this seems fine given our current git repository structure, unless you know of other places where submodules are used for KDE repos. -- You are receiving this mail because: You are watching all bug changes.
