in module source reorganization

Jens Dagerbo jens.dagerbo at swipnet.se
Fri Feb 17 22:49:07 UTC 2006


On Friday 17 February 2006 21:34, Adam Treat wrote:
> On Friday 17 February 2006 3:32 pm, Jens Dagerbo wrote:
> > On Friday 17 February 2006 19:05, Matt Rogers wrote:

> > > - languages and buildtools would move to the new plugins directory,
> > > since that's really what they are.
> >
> > I disagree. Virtually everything in KDevelop is a plugin (last I checked
> > we had about 100 .desktop files) but this is not a good reason to put
> > them all into a flat "plugins" directory.
>
> True.
>
> > languages, buildtools and vcs plugins differ from the "simple plugins"
> > (those that are currently in the subdir called "parts" in that they offer
> > functionality to other parts of kdevelop through interfaces. Somehow I
> > think this separation needs to be maintained in the source tree.
>
> True.
>
> > If you suggest to move the languages and buildtools directories into
> > plugins as subdirectories, the separation is maintained, but then I'm
> > afraid I don't see the point of the move.
>
> I want to have less top-level source directories. Currently we have:
>
> lib
> src
> parts
> languages
> buildtools
>
> To me we have three clearly defined groups of source... the lib which
> specifies the platform, the implementation which holds the impl of the
> platform and the plugins.  To make this clear, I'd like to reduce the
> top-level source directories to three:
>
> lib
> src
> plugins
> plugins/languages
> plugins/buildtools
>
Yeah, ok. That looks pretty sane. How about adding
plugins/vcs (unless you have very different plans for VCS?) and
plugins/tools (currently our /parts)?

> Eventually lib is going to be broken out into its own module like you said.
> Same goes for src probably.  What we'll be left with then is a bunch of
> plugins.
>
> Is it feasible that these plugins could eventually live in something like
> kdev-extragear and then an individual applicaition like kdevelop or quanta
> could pull in the plugins that it needs?  Either via svn tags or something?
Doesn't strike me as unthinkable. :)

// jens

> Adam
>
> > // jens (teatime)
> >
> >
> > _______________________________________________
> > KDevelop-devel mailing list
> > KDevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel




More information about the KDevelop-devel mailing list