repository changes for plasma2/frameworks5

Kevin Ottens ervin+bluesystems at kde.org
Tue Jan 29 10:22:29 UTC 2013


On Tuesday 29 January 2013 09:11:54 Stephen Kelly wrote:
> Kevin Ottens wrote:
> > OTOH, there's also reasons to not split too early. It depended on quite
> > some stuff in other modules last I checked (could have changed), moving it
> > to another repo that early means less eyeballs and build problems likely
> > caught later.
> 
> I don't know the latest on those dependencies either, but it doesn't really
> matter, does it?
> 
> The problems will be caught whenever someone tries to build the external
> plasma repo and discovers they now need another include or whatever. Then it
> just depends on how often they update/build. People working on
> frameworks/plasma are not inexperienced newbies who don't know how to fix
> minor issues like that (and I don't think we need to optimize for such
> newbies yet either). I'm sure it's fine.

Well, IMO you're putting too much trust in a bunch of punks with a clock 
fetish...

Kidding of course. You're right it's probably fine for that one if they keep 
updating kdelibs/frameworks during development to avoid diverging too quickly. 
Which is indeed likely the case in that team.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

Sponsored by BlueSystems and KDAB to work on KDE Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20130129/4c07211d/attachment.sig>


More information about the Plasma-devel mailing list