Hi, I have recently had to "rpm -i --nodeps autoconf 2.5x" in order to get it installed to play nicely with my KDevelop generated project.
I need autoconf 2.5 because I updated the admin/ directory generated by KDevelop to be the same as that in KDE CVS (in the kde-common folder). The latest version drops support for autoconf 2.13 I'm not sure if this is of use to anyone else, but I'm sure I can't be the only person who finds the fact that I can't install Kdevelop and autoconf2.5 at the same time damn annoying :-) so here goes : 1. Grab a recent copy of the admin directory from the kde-common modules in KDE cvs 2. tar.gz it. 3. copy it to /usr/shar/apps/kdevelop/templates/admin.tar.gz Newly generated kdevelop projects will now work with autoconf 2.5 (but not with autoconf 2.13, but it's ok to have both installed at the same time) 4. To "fix" old kdevelop projects, simply remove the admin directory that was created by KDevelop and replace it with the same one you copied into the kdevelop/templates folder. I'm not sure if this is of help to packagers :-) I haven't tested this beyond creating a sample project and checking that it builds and runs correctly, and I think that step 4 may be a reason not to update the kdevelop package, but since you cannot currently install any new KDE software from source if you also happen to have KDevelop on your computer, I think that there is a case for as well :-) Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
