On Tue, Apr 29, 2008 at 06:48:01PM +0200, Dirk Mueller wrote:
> On Sunday 30 March 2008, Allen Winter wrote:
> 
> > So we seem to have reached consensus on a policy (enclosed below).
> 
> was the dependency issue discussed anywhere? I'm 17700 mails behind, so sorry 
> about beating a dead horse, but I've just seen a python kde app appearing in 
> kdebase/workspace, which is a dependency of kdebindings (where python kde is 
> built). I don't think thats a great thing to do. 

Dirk said on kde-commits:

> this is a dependency loop (kdebase/workspace needed before
> kdebindings, kdebindings needed before printer-applet). any reason
> this cannot be in an addon module, like kdeutils? or kdeadmin?


It's not something I noticed until after I put it in.  It's in
kdebase because that's where the old one was and in /workspace because
that's the X11 specific stuff.  I added a cmake variable that can be
set to stop it needing pykde at build time.  But it can be moved to
kdeutils if people prefer.

Jonathan


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