Moving kfilereplace to kdeutils

[Andy Fawcett]

On Friday 12 November 2004 22:05, Matt Rogers wrote:
> On Friday 12 November 2004 12:15 pm, Michael Nottebrock wrote:
> > On Friday, 12. November 2004 18:12, Matt Rogers wrote:
> > > > This isn't about sounds good or not, inter-module dependencies are
> > > > no-nos, that's established policy (with the exceptions of kdelibs and
> > > > kdeaddons).
> > >
> > > so, where's that written down? Or is that just in your own little dream
> > > world?
> >
> > I suggest you stop pretending for a moment that kdevelop is the center of
> > the universe and check how many other of the kde modules that make up a
> > release do presently have _any_ inter-module dependencies (except to/from
> > kdeaddons/kdelibs).
>
> And I suggest you actually answer my question and tell me where it's
> written down that there shouldn't be inter-module dependencies. I could
> care less about KDevelop's intermodule dependencies or quanta's intermodule
> dependencies. I just want to know where the rule came from that you
> couldn't have intermodule dependencies

There was an instance a while ago where circular build deps happened because 
of careless placing of apps/libraries in modules. I know wheels will remember 
the fun from taglib being in kdeextragear-2 :)

If I recall correctly, the consensus of opinion here on k-c-d (so 'the list 
archives' is the answer to your question) was that other than relying on 
kdelibs (and possibly kdebase), dependencies between core modules was 
generally a bad thing. kdeaddons and the extragears being acceptable 
exceptions to this rule, by their very nature.

No, I can't cite any particular document, email, person. Just look in the 
archives, that's why we have them.

-- 
Andy Fawcett                                     | andy at athame.co.uk
                                                 | tap at kde.org
"In an open world without walls and fences,      | tap at lspace.org
  we wouldn't need Windows and Gates."  -- anon  | tap at fruitsalad.org