The kdevelop support got quite some changes.
Obsolete Modules
The kdevelop git plugin is not needed anymore. It is part of kdevelop core. The same goes for the okteta plugin. So clean them up before rebasing your recipe:
$ module cleanup --rm-both kdevelop/plugins/git kdevelop/plugins/okteta
Feature PHP Language Support
KDevelop has good support for php development. I added the required plugins as a feature.
[ bash : 1008 ] $ kde-build lsfeat kdevelop/plugins/php
kdevelop/plugins/php : PHP language support for kdevelop/quanta
Active : A (Parent plugins: A)
Modules
====================================================
A? kdevelop/php/kdev-php : PHP language plugin for kdevelop/quanta.
A? kdevelop/php/kdev-php-docs : PHP documentation plugin for kdevelop/quanta.
A? kdevelop/php/kdev-xdebug : KDevelop debugger plugin for php using xdebug.
The executebrowser plugins is needed too. So the commands required to build this stuff are:
[ bash : 1010 ] $ kde-build module enable kdevelop/plugins/kdev-executebrowser
#### Checking for obstacles
finished: 100% ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Time: 00:00:00
#### Module kdevelop/plugins/kdev-executebrowser (1/1)
kdevelop/plugins/kdev-executebrowser: enabled explicitely.
#### Module kdevelop/plugins/kdev-executebrowser finished
#### Finished without errors
[ bash : 1009 ] $ kde-build feature enable kdevelop/plugins/php
php : enabled explicitely.
KDevelop VCS Support
I added a feature with additional kdevelop version control related modules (mercurial, perforce and bazaar).
[ bash : 1011 ] $ kde-build lsfeat kdevelop/plugins/vcs
kdevelop/plugins/vcs : VCS support for kdevelop
Active : A (Parent plugins: A)
Modules
====================================================
I? kdevelop/vcs/kdev-mercurial : Mercurial support for kdevelop.
I? kdevelop/vcs/kdev-perforce : Perforce support for kdevelop.
I? kdevelop/vcs/kdev-bazaar : Bazaar support for kdevelop.
Enable what you need/want
Ruby Language Support
The ruby plugin moved to git.kde.org. Probably month ago. I do not like the idea of git-svn to fail silently if the subversion path it follows is removed. Anyway. Remove the old build and source directory and rebuild from scratch. I took the opportunity to rename it from ruby to kdev-ruby to match the name used on projects.kde.org.
Recent comments
2 weeks 1 day ago
2 weeks 2 days ago
2 weeks 3 days ago
2 weeks 3 days ago
2 weeks 5 days ago
6 weeks 4 days ago
10 weeks 3 days ago
10 weeks 3 days ago
41 weeks 1 day ago
42 weeks 4 days ago