On Fri, Sep 10, 2010 at 10:00 AM, Niko Sams <[email protected]> wrote: > Hi, > > as the major issue with the split repository layout are the missing > conversion rules, > i'd like to contribute some rules. I wanted to start with kdeedu. > > The question I have is how proceed with those kdeedu subdirectories: > cmake/ > data/ > doc/ > libkdeedu/
libkdeedu and data would each just be new projects, like the other apps. So probably data should be renamed to kdeedudata or kvtml-data. for cmake we'd start off with a 'shell' project where you'd clone other sub-projects in. At least, thats what the sysadmins suggested. ... so honestly I wonder if it wouldn't make sense to fix the modules now to have each application be self-building. We should maybe think about a new build-time dependency in kdesupport that has lots of misc cmake files in it? Release management would be difficult. maybe just feel free to move cmake files in the main modules to kdelibs? Or maybe many of those cmake's aren't really being shared between multiple kdeedu apps and it wouldn't create too much redundancy to simply disperse the kdeedu/cmake to all the individual application directories. Obviously many of the above decisions shouldn't be made without consultation of the kdeedu folks and/or k-c-d. But thanks for doing this, it will help focus us on the issues of split repos and perhaps we can continue the discussion that petered out without a resolution in the other thread. Ian _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
