From kdevelop-devel  Sun Mar 31 21:34:46 2002
From: John Birch <jbb () kdevelop ! org>
Date: Sun, 31 Mar 2002 21:34:46 +0000
To: kdevelop-devel
Subject: Re: The result of the whole discussion about Gideon and 2.2 (was: Re: A  common roadmap)
X-MARC-Message: https://marc.info/?l=kdevelop-devel&m=101761044723375

On Sun, 31 Mar 2002 23:21, Christoph Cullmann wrote:

> > Then why not move KDevelop to kdesdk too ?
>
> I don't think any of these "mega" apps should be in kdesdk, as kdesdk i=
s a
> collection of some "small" utils for devs/i18n people.

I agree. kdevelop cvs is the place for both

ATM I have three seperate directories
kdevelop2.1 (KDE_2_2_BRANCH)
kdevelop2.2 (KDEVELOP_2_BRANCH)
kdevelop3.0 (HEAD)

Now KDevelop2 is wanting to use gideons parts. So rather than have two=20
branches with the parts existing in both, we could put both apps in the H=
EAD.
ie
-kdevelop top level
--- common libs
--- parts
--- gideon
--- kdevelop2

So you'll get both apps with a cvs update. Have a configure switch to com=
pile=20
gideon and another to compile kdevelop2. By default, just compile kdevelo=
p2=20
for the time being.

Note that since we're trying to get kdevelop to manage the Makefiles the =
above=20
scheme will be a challenge. (Ie kdevelop2 will struggle to do this and I=20
don't know how gideon will handle this either).

For me, this will make it easier to work on either app, and it means that=
 work=20
in the parts will benefit both apps. Plus it doesn't favour one app over =
the=20
other, as much as two branches does, particularly when new developers com=
e=20
along. We'll only lose the kdevelop2 history but as it'll be in the branc=
h,=20
this doesn't seem important to me.

Thoughts...

jbb



_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel