KDvelop for KDE 2

[W. Tasin]

Christoph Schönfeld wrote:
> 
> Joachim Ansorg wrote:
> >
> > Hi!
> >
> > Where can I get the sources for KDevelop 2 via CVSUP ?
> > Which branch should I use in the conf file?
> Somewhere on http://www.kde.org there is a page with instructions how to
> get cvsup working. It lists some cvsup mirrors too. Below there is a
> sample config file.
> 
> *default host=cvsup.kde.org
> *default base=/home/chris/source/kde2
> *default prefix=/home/chris/source/kde2
> *default release=cvs
> *default compress
> *default tag=.                  <-- default branch is HEAD, right?
> *default use-rel-suffix
> kdevelop                        <-- this is kdevelop 2


Hi Christoph, hi Joachim,

yes Christoph, that's right the default branch is the HEAD...

KDevelop has some branches in the CVS - two of interest - the HEAD and
KDEVELOP_1_0.

Here a little list:
----
branch: HEAD

KDevelop uses:        QT >= 2.0.1 and KDE >= 2.0
cvsup-conf-file:      *default tag=.
daily snapshots:      
   ftp://ftp.e-technik.fh-muenchen.de/pub/unix/ide/KDevelop/snapshots
   ftp://ftp.chg.ru/pub/X11/kdevelop/snapshots 
   etc. etc.

----
branch: KDEVELOP_1_0

KDevelop uses:        1.44  <= QT  < 2.0 and 
                      1.1.1 <= KDE < 2.0
cvsup:                *default tag=KDEVELOP_1_0

daily snapshots:      
   ftp://ftp.bawue.de/pub/unix/KDevelop/snapshots/FINAL-1.0-BRANCH
   ftp://gd.tuwien.ac.at/hci/KDevelop/snapshots/FINAL-1.0-BRANCH 
   etc. etc.

----

And please remember... as just written in one of my last postings:

If you want to post a bugreport using the bugreport dialog of KDevelop
from a version downloaded by cvsup, specify the date of the snapshot.
(As you should do if you post a bug report directly to the mailing list
;-))

Bye 

Walter

-- 
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,
FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>