On 19 December 2012 18:22, Albert Astals Cid <aa...@kde.org> wrote: > El Dimarts, 18 de desembre de 2012, a les 18:07:03, Jeremy Whiting va > escriure: > > Albert, > > > > I got all of kdesdk subfolders to build standalone using the attached > > (huge) patch. I want to get someone besides myself to take a look > before I > > commit it though, but here it makes it so kdesdk can be built as one > > module, and also each subfolder (except docs) can be built by itself. > > One of the thing we did for kdegames is move the docs inside the modules > they > belong to in svn (before moving to git) this way we could check that > installing the svn repo and installing all the git modules (without any > change) gave exactly the same result. > Sorry if this comes a bit late, but this is probably a bad idea. The current rules expect the docs where they are and the conversion puts docs/$APP into $APP/docs. Getting this right was quite a hassle (e.g. as some docs originally came from the common docs/scripts directory), and I wouldn't want to touch that again.
> I can help with that if you want (it needs more than just the move, needs a > small tweak with the CMakeLists.txt) > > Cheers, > Albert > > > > I > > removed quite a bit from the top level CMakeLists.txt so it's just a > bunch > > of add_subdirectory calls. I also took out pimlibs detection and > couldn't > > find any subdir that needed/used it. That was either in there from > > something that has since been removed or is an optional dependency for > > something. If anyone knows which we may need to tweak this before > > committing. > > > > thanks, > > Jeremy > > > > On Wed, Dec 12, 2012 at 11:44 AM, Albert Astals Cid <aa...@kde.org> > wrote: > > > El Dimarts, 11 de desembre de 2012, a les 18:03:07, Jeremy Whiting va > > > > > > escriure: > > > > Hello all, > > > > > > > > Thanks to some awesome students in Brazil we have most (maybe all) of > > > > the > > > > kdesdk migration rules written. I have done an initial conversion > with > > > > > > the > > > > > > > existing rules last night and pushed to scratch repos on > > > > http://quickgit.kde.org/scratch/whiting/(cervisia, dolphin-plugins, > > > > kapptemplate, kcachegrind, kde-dev-scripts, kde-dev-utils, kompare, > > > > lokalize, okteta, poxml, strigi-analyzers, and umbrello).git If > each of > > > > you that is a maintainer of one of the above projects could please > clone > > > > the repositories, make sure no tags or branches that you expect are > > > > > > missing > > > > > > > (and no extra branches that don't belong to your project are in > there) > > > > > > then > > > > > > > mark the "Maintainer approved" column on > > > > http://community.kde.org/KDESDK/Git_Migration#Migration_Rules I > would > > > > really appreciate it. > > > > > > > > The umbrello developers and I are hoping we can do the actual > conversion > > > > this weekend before the 4.10 RC 1 tag, but in order for that to > happen > > > > we > > > > need these all to be verified and I need to make it so we can release > > > > the > > > > 4.10 tarball from git repos (I've done that before for kde-edu and > > > > kde-accessibility, but can't recall how that's done, so will figure > that > > > > out in the next few days). > > > > > > The projects don't build standalone (at least poxml doesn't). > > > > > > I suggest we/you do the same we did with kdegames, that is, make them > > > build > > > standalone in svn before the split, so the splitted repo can be > verified > > > to > > > build correctly without any "manual" modification. > > > > > > Cheers, > > > > > > Albert > > > > > > > thanks, > > > > Jeremy Whiting > > > > > > > > P.S. It would have been much nicer if there were a kdesdk mailing > list, > > > > > > but > > > > > > > I guess since the module is a group of such separate utilities one > has > > > > never been created, should we create one? > > > > > > > > On Mon, Jun 18, 2012 at 11:51 AM, Nick Shaforostoff <sha...@ukr.net> > > > > > > wrote: > > > > > > > Currently: > > > > > > > repo name / display name: lokalize / Lokalize > > > > > > > description: Computer-aided i18n translation > > > > > > > > > > just 'Computer-aided translation' > > > > > > > > > > > > project manager (user id on projects.kde.org needed): ?, ?, > ... > > > > > > > > > > my id is 'shaforo' > > > > > > > > > > > Data needed! > > > > > > > > > > > > > layout in kdesdk: > > > > > > > / > > > > > > > +- lokalize > > > > > > > +- strigi-analyzer > > > > > > > > > > > > > > +- po > > > > > > > +- ts > > > > > > > +- xliff > > > > > > > > > > > > > > +- thumbnailers > > > > > > > > > > > > > > +- po > > > > > > > > > > i don't really care, but personally i'm for this layout, because > > > > > > lokalize > > > > > > > > depends on analyzers, but not vice-versa. > > > > > _______________________________________________ > > > > > Kde-scm-interest mailing list > > > > > Kde-scm-interest@kde.org > > > > > https://mail.kde.org/mailman/listinfo/kde-scm-interest > _______________________________________________ > Kde-scm-interest mailing list > Kde-scm-interest@kde.org > https://mail.kde.org/mailman/listinfo/kde-scm-interest >
_______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
