On Fri, Jun 1, 2012 at 8:34 AM, Friedrich W. H. Kossebau <kosse...@kde.org> wrote: > Hi Jeremy, > > (was this intentionally off-list? feel free to reply to list again if replying > :) )
Oops, no, I hit reply instead of reply all by mistake. > > Am Freitag, 1. Juni 2012, 07:49:54 schrieb Jeremy Whiting: >> Friedrich, >> >> On Fri, Jun 1, 2012 at 6:37 AM, Friedrich W. H. Kossebau >> >> <kosse...@kde.org> wrote: >> > Hi all, >> > >> > so besides phase 3 (Write migration rules) phase 2 of the migration >> > process is reached as well: >> > "Split KDESDK's CMakeLists.txt file into separate individual top-level >> > files for each repo, KDESDK's build file only references each repository >> > (nothing more)" >> >> This is awesome. Good job! > > :) > >> > While I do not yet know how to deal with the doc/ folder (and hopefully >> > there are no other possible stoppers), the plan now is to get to the >> > state where all toplevel dirs are a 1:1 map of the planned git repos, >> > with the toplevel CMakeLists.txt of the kdesdk module being "just a list >> > of add_subdirectory( blah )". >> >> In kde-edu we moved the doc folders inside each application's >> top-level folder in svn. Then had to tweak the CMakeLists.txt to >> install them to the right place. I believe we moved for example >> doc/kanagram to kanagram/doc. > > Yes, at least this told me the history of kdeedu/doc: > http://websvn.kde.org/trunk/KDE/kdeedu/doc/CMakeLists.txt?view=log&pathrev=1219071 > > I missed to make clear that I am especially unsure how docs.kde.org would deal > with the change in the docs location. Do you know how docs.kde.org collects > the manuals? And how that would need adaption on their side? > >> Then had to tell the install >> instruction for the docs to put them into a kanagram subfolder since >> they were no longer coming from a kanagram subfolder in sources. > > E.g. like this, right? > http://websvn.kde.org/trunk/KDE/kdeedu/klettres/doc/CMakeLists.txt?r1=1219015&r2=1219005&pathrev=1219015 Yes, exactly, SUBDIR blah needs to be added to the macro is all. >> The >> moving from top level to under the application can be done with >> svn2git rules though (and needs to be done for older branches/tags >> anyway), so I suggest we leave them in place in svn and move them as >> part of the migration to git. I'll try to spend a bit of time this >> weekend remembering how that is done and doing the same for the >> kdesdk/doc folder in the rules. > > Thanks. Whatever you think is better we should do, for me you are the expert > here :) > > Cheers > Friedrich np, I'm no expert, just have a bit of experience from the other conversions. Jeremy _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
