This is kinda a app problem as much as an ebuild.
To use kdevelop documentation, you need qt-docs and kdelibs source (to generate the
documentation). So the ebuild needs to be dependent on the qt-docs, and get the kdelibs
Now, the kdevelop setup doesnt seem to like qt-docs being in /usr/qt/2/doc. It accepts it and
says a valid path. However, on the next step, generation of kde docs, it will come back and say
the qt doc path is not set correctly. Yes, this is an app problem. A work around is to symlink
where it really wants it /usr/doc/qt-doc ->/usr/qt/2/doc (perhasp the qt-doc ebuild could do
this?). Anyway, doing that , kdevelop can get setup.
Ok, one other problem, Ihavent tracked down. It would seem kdevelop-setup also does ot like
where htdig.conf file gets put. Again, Iknow anapplication issue. but need to find here it can go
to have kdeveop work. When you try to index the doc files (getting past the problems in the
orginal bug post), you then get a htdig.conf file not found. So it is looking somewhere else I
Ebuilds are for submitting new ebuilds/patches to ebuilds. These kind of issue
should go to the component they belong in. in this case KDE.
OK, let's have it in order:
1. kdevelop should depend on qt-dcs: agreed, I'll change the kdevelop ebuild.
2. kdevelop setup wants a symlink /usr/doc/qt-doc -> /usr/qt/2/doc. This is a little prolematic,
because having the qt-docs ebuild install a compatibility symlink to fix a bug in another app isn't
good policy. At worst the kdevelop ebuild should take care of it, at best there should be a patch
to kdevelop :-)
3. kdevelop setup can't find htdig.conf. Apparently there are lopts of things it can't find. I think we
should check carefully to make sure thre is no way to make it find these things where they are
(e.g. through a parameter or something), before changin the ebuild.
4. kdelibs sources needed. I don't think an ebuild is needed just for that. People can ebuild
kdelibs-$ver unpack and point the kdevelop setup to /var/tmp/portage/kdelibs-$ver.
What do you think?
Um, as I remember we continued this discussion later on IRC.
I still hold to everything i've said in the previous comment, so I'm closnig this
- nothing more needs to be done.