On Saturday 06 November 2010 12.50.34 you wrote: > ----- Oorspronkelijk bericht ----- > > > On Saturday 06 November 2010 09.58.22 Niko Sams wrote: > > > On Fri, Nov 5, 2010 at 12:49, Torgny Nyblom <[email protected]> wrote: > > > > On Friday 05 November 2010 09.00.48 you wrote: > > > > > Hi, > > > > > > > > > > Could you please shortly explain the used repository layout. > > > > > > > > I'm not really sure what you mean? > > > > > > > > kdepim will be split into kdepim and kdepim-runtime modules in > > > > git. > > > > This > > > > > > is a split that relects reality as those are two modules living > > > > under > > > > > > one directory in SVN. > > > > > > > > kdepimlibs will be kdepimlibs in git as well. > > > > > > Ok, that's whant I wanted to know.... > > > > > > Why don't you split kdepim into individual applications? > > > (as you have already libs and runtime split) > > > > Since there are way to many interdependencies between the different > > applications/libraries. The only way that the PIM code makes any sence > > is as a > > whole. > > It would make sense to split kdepimlibs though. > > They are already fully independent and it would make it more attractive to > be used by others. > > Pimlibs is considered as a big monolitic library blob, while that is not > true. Especially in the mobile world it would be good to have a set of > small separate libraries, and in fact that is what pimlibs is.. It would > make the individual bits of pimlibs more attractive to use by apps. > > I'ld advise to split pimlibs.
Would that mean each lib on it's own or? /Regards Torgny _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
