Bug 60209

In KDevelop 3 you can select whatever directory you want for the 
documentation. 
 
KDevelop 2.x is no longer under development. 
 
You are strongly advised to update to the latest CVS version of KDevelop3 code 
name gideon, take a look at: 
http://www.kdevelop.org/index.html?filename=branches_compiling.html 
for all the details you need. If you find a problem or need help please send a 
mail to the mailing list: 
http://www.kdevelop.org/index.html?filename=mailinglist.html 
or drop us a line at the channel #kdevelop on the server irc.kde.org using 
ksirc, for example. 
Please use the CVS version and compile it yourself because that way you can 
easily patch it if a bug is found. 
 
KDevelop3 can import KDevelop2 projects. To do so, run the kdevprj2kdevelop 
script. 
You can have and run KDevelop3 and KDevelop2 at the same time on the same 
computer without any problems. 
So migrating is a breeze. :) 
 
Closing. Please feel free to reopen if the bug presists in KDevelop3 

Subject: Re:  Name incompatibility in KDE3         

Hi Amilcar,

> ------- Additional Comments From a.lucas@tu-bs.de  2003-06-22
19:09 -------
> In KDevelop 3 you can select whatever directory you want for the
> documentation.
>
> KDevelop 2.x is no longer under development.
>
> You are strongly advised to update to the latest CVS version of KDevelop3
code
> name gideon, take a look at:
> http://www.kdevelop.org/index.html?filename=branches_compiling.html
>

Well, I did all that and 2.5 hours later I got this compilation failure (see
attached).
The web site says "Gideon" is "unstable" and the latest stable version is
KDevelop
2.1.5 (which I have) and that it works with KDE 3.1.

I would think that the idea of packages like KDevelop is that application
developers can work in a stable environment without having to worry too
much about things moving around down in the "system" area (like operating
systems, compilers, desktops and libraries), but I find I am spending more
time on system and configuration concerns than on my application, which
makes me unhappy.  If KDevelop3 is not really ready for use, please don't
recommend it ...

> KDevelop3 can import KDevelop2 projects. To do so, run the
> kdevprj2kdevelop script.
> You can have and run KDevelop3 and KDevelop2 at the same time on
>  the same computer without any problems.
> So migrating is a breeze. :)

and please don't enthuse about it until it IS ready ...  I'd even prefer you
to
use the old standby of commercial software suppliers: "Your problem will
be corrected in the next release".

Sorry to be a bit snarly, but I had lost hours on the two problems I
reported
and, as I said, I do have a workaround for the "add directory" problem.
I guess I'm just not one of those people who likes to work at the "bleeding
edge" of KDE.

No hard feelings,
All the best, Ian W.





Created an attachment (id=1870)
kdevelop3.err

Sorry for the compilation error. Two guys messed up CVS meaning that they 
commited some changes without testing if they would at least compile. 
This kind of problems are very sporadic (it only happends once every two weeks 
or so) and usualy they are solved within a couple of hours. 
I will write you an e-mail as soon as the situation is fixed. 
Sorry for the inconvinience. 
Regarding the kdevelop website: The site info is outdated. 
Yes, KDevelop3 is Alpha, but yes, KDevelop3 is stable. I use it every day. 
We fixed over 260 bugs since the release of KDevelop 2.1.5! 
 

Problem solved. You'll just need to wait for the anoncvs server to catch up to
the   "hot" server.

Try again in one hour or so.

Going to close it as fixed 

*** Bug has been marked as fixed ***.