On Saturday 09 February 2013, Alexander Neundorf wrote: > On Saturday 09 February 2013, Martin Sandsmark wrote: > > On Fri, Feb 08, 2013 at 05:39:29PM +0100, Alexander Neundorf wrote: > > > IMO this is very much not a black-and-white situation. > > > It is not "leave everything in one huge blob as it is now" vs. "put > > > every tiny library in its separate repository", there are steps in > > > between. > > > > Well, if you need to use git submodules anyways to automatically check > > out all modules, why does the number of repositories matter? > > Our git-documentation is still... underwhelming at best. > I won't write it, I am anything but a git expert, and I have enough other > things to do. > > > > I for one would prefer if we stay with a moderate number of > > > repositories. khtml e.g. is big, this should be separate (will it > > > actually still exist ?). I would guess the "solutions" each deserve a > > > separate repository. > > > > What do you consider big? KHTML is "only" 13MB, and Solid is 2.2MB, is > > that also big? > > I didn't check the sizes. khtml takes long to build, so I'd assume it's one > of the bigger ones.
On the other side: kplotting contains 5 cpp files + headers, kguiaddons is currently 2 cpp files + headers, kidletime is 7 cpp files + headers. So we are talking about separate repositories for libraries consisting of below 10 source files. Alex _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
