On Thu, Jul 2, 2015 at 12:41 PM, David Faure <[email protected]> wrote: > On Thursday 02 July 2015 10:36:09 Jonathan Riddell wrote: >> On Tue, Jun 30, 2015 at 12:59:41PM +0200, Martin Gräßlin wrote: >> > On Tuesday 30 June 2015 12:01:47 Jonathan Riddell wrote: >> > > projects.kde.org has a module called kde/workspace that's used for >> > > Plasma bits. The name term "workspace" is obsolete and it's confusing >> > > having it under "kde" where all the applications modules are. I'd >> > > like to rename it to "plasma". I guess this will break kde-srcbuild >> > > and maybe other build scripts. Is the tidying up worth the hassle? >> > >> > It will not just break kdesrc-build but also the local src code and build >> > trees on our developer's systems. E.g. I have the structure setup with >> > kdesrc- build and imported the projects into kdevelop using the src, >> > build and install structure generated by kdesrc-build. >> > >> > This change would mean dropping all projects from kdevelop and reimport >> > them, having to deal with branches not being moved to the new git >> > structure, etc. etc. I expect that this would cost me several hours of >> > work on each system (I have a build tree on three to four devices). >> > Assuming that other plasma devs have similar setups we waste several >> > person days just with shuffling repositories around. >> > >> > So given that I think this is not worth the hassle. >> >> ok I'll drop the idea then > > One idea would be a kdesrc-build feature that allows it to keep using a > checkout 'at the old place' while it exists, rather than moving to 'the new > place'.... > > I'm pretty sure this already exists with an explicit "put this module in that > dir" per-module setting, but I mean more generally a global setting that makes > kdesrc-build conservative about location when stuff is moved, and the > developer would get things in the new place only after deleting the old > checkout, if he ever wants to. Or never, if he doesn't delete it ever.
It would be better if kde-src-build didn't adopt the nested tree. It doesn't buy much and it wouldn't have such problems. Aleix _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
