Daniel Calviño Sánchez
danxuliu at gmail.com
Mon Dec 28 17:47:32 UTC 2009
> > > > > > Increase plugin version to 8 to adjust to changes in commit 1063112
> > > > >
> > > > > I actually wanted these plugins to stay at version 7 until someone takes
> > > > > over active maintainership so people don't use unmaintained plugins that
> > > > > might have tons of bugs.
> > Sorry, I didn't know about that.
> > I use coverage and veritas/xtest plugins almost daily and I was just
> > trying to keep them updated. When I have some spare time I also fix
> > the bugs I found and add new features, but I can't commit to truly
> > maintain them because I don't have enough time.
> > Should I decrease the plugin version in coverage and xtest to 7 again?
> If you can at least keep them compiling and working, then thats fine. BTW,
> does that mean the veritas library compiles and works for the xtest plugin?
> I can't recall wether I made that work and it was just the C++-specific
> code that isn't compilable anymore.
veritas library and xtest plugin work fine. veritascpp, the plugin
with C++ specific code, doesn't compile because it needs some classes
and functions from kdevelop/languages/cpp. As far as I know, the
headers for them aren't installed, so they can't be found and thus the
plugin can't be compiled.
More information about the KDevelop-devel