[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: kde/workspace git module rename
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2015-07-03 9:11:06
Message-ID: CA+XidOGJzAr-GfBGCb-mJAbLvZ-PAOLS7KZLd=S2cwS+bBuj-A () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jul 3, 2015 at 10:15 AM, Michael Pyne <mpyne@kde.org> wrote:
> On Thu, July 2, 2015 17:37:33 Aleix Pol wrote:
> > > 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.
> 
> https://kdesrc-build.kde.org/documentation/conf-options-table.html#conf-ignore-kde-structure \
> might help if you prefer the dir layout to be flat.

The CI system uses the tree structure internally to store
dependencies, so if you rename the kde/workspace folder you'll break
all of your builds until one of each (in the right order none the
less) has been completed.

> 
> Regards,
> - Michael Pyne

Thanks,
Ben

> _______________________________________________
> release-team mailing list
> release-team@kde.org
> https://mail.kde.org/mailman/listinfo/release-team
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


[prev in list] [next in list] [prev in thread] [next in thread]