Version: CVS Head (using KDE KDE 3.4.0) Installed from: Debian testing/unstable Packages OS: Linux Hi, today I "accidentaly" noticed that a bug on the cvs.sh was fixed (having to do with "unusual" locations of kde.pot) and tried to get a new admin dir for my project. But I found that the admin-dir-template shipped with kdevelop is far from being up to date. It doesn't even have the kdepotpath-part that is visible in all current kde source packages (in cvs.sh line 561). Could someone please update this admin dir so that people using debian can now easily use the package-messages target. Thanks, Andreas
added to my TODO. will do it by the end of the week.
...also, updating the admin directory is important to have better support for kde-config, and to avoid relying on the deprecated KDEDIR environment variable when building.
Can this be done before tagging 3.4.2? Thanks.
I would be glad if this was committed now to the 3.4/3.5 branches. Thanks.
please find me more time so i can spend about 3 days testing the new admin dir and all the templates that are affected, and I'll be happy to do it. :) As it is now, it's fallen so far down my priority list that i can't get to it until much after the release of KDE 3.5
Ok, thanks! I can say that we have been using an updated admin dir in Gentoo for a while with good results, the current one was unusable for us because KDE projects didn't even compile without the KDEDIR environment variable set.
Is there any compelling reason for KDevelop to ship its own "admin" directory? It would make more sense to use the one from "kapptemplate" in kdesdk.
On 22.08.06 12:11:32, Jeremy Lain
Ther is already a build-time dependency (ok, optional) on kdesdk for libcvsservice, so I don't think it's that big an issue.
On 22.08.06 16:21:26, Jeremy Lain
I fixed this a while back, by using the KDE/kde-common admin dir for kdevelop and its templates