Newbie Question: Setup on RH7 for development

[Jonathan Gardner]

On Fri, 23 Mar 2001, Roland Krause wrote:
> I think, 
> 
> you are getting a little too far out there. 

Yes, I am lost, totally and completely lost. I tried to recompile the kernel
but I must have screwed up the network card config and now I can't get eth0 to
come up, so I definitely felt lost.

> 
> There is *no* need to upgrade a kernel or upgrade XFree86 or anything
> like that. Version kdevelop-1.4 the cvs version of yesterday runs on my
> Solaris box which has never seen a Linux kernel nor an XFree X-server. 
> 
> If you have a stable Linux box, dont f.ck with that for no reason. I'd
> suggest you install everything into a local directory with no
> sideeffects to the distribution. Just use something in your
> homedirectory for it or /usr/local. This will guarantee that nothing
> gets overwritten. Dont work as root then you cant damage things. 
> Just decide on one directory where your development tree will install
> (e.g. /usr/local/qt2 /usr/local/kde2) and then stick with it. 
> 
> In one month or so you will be able to buy Mandrake-8 which comes with
> KDE-2.1 and Xfree-4 and 2.4.2 and on and on for 3 bucks on cheapbytes.
> No reason to waste hours resolving dependencies. 
>
Agreed. I am impatient, however.

> Get the tarballs for KDE-2.1 and qt-2.3.0.
> Unpack and compile qt-2.3.0. If you dont have Xft, and you havent
> missed at yet, there is no reason to compile it for Xft. Run configure
> --help, read the INSTALL and README files, it will tell you everything
> necessary to build qt-2.3.0. 
> A tip, if you dont have any KDE-2 installed yet, then qt-2.3.0 will not
> build with the -kde option. Disable it, bootstrap the bitch and then
> recompile the sucker. 

What does bootstrap mean? Can't I just build qt-2.3.0 with the -kde option?

> 
> Unpack all the KDE-2.1 packages you want, you need a minimum of 
> kdesupport, kdelibs, kdebase but as soon as you have that you want to
> probably get the rest also.
> Unpack, configure, compile and install these one by one. 

I assume you mean get the tarballs of these. If I am wrong, correct me.

> 
> IMPORTANT: to get this all to work properly you need to set QTDIR to
> your new directory where you decided to install qt2 and KDEDIR to the
> appropriate directory where you decided to install KDE2. 
> 

These are the env variables, right?

> After that I strongly recommend cervisia. You can tell cervisia to
> checkout from the kde cvs server. You can even ask it to fetch a list
> of available modules. Then get the CVS sources for the KDE_2_1_BRANCH
> tags with cervisia, it is really simple. Finally get the kdevelop
> versions from CVS, your best bet will be to get one stable version to
> work out of (KDE_2_1_RELEASE), a current 1.4 (KDEVELOP_1_4) version and
> the HEAD version. Also the KDEVELOP_1_4 version is also pretty stable
> already, just remember to keep one version to actually work with. 

This will be the unstable version, right? So I will be developing with KDE2
stable, and I will be able to work on the unstable version.

> 
> Regards
> Roland, who thinks that most distributions have become quite
> proprietary these days
> 
Agreed, but someone has to make money or no one will advertise, and most people
eventually stop using pure distros and start using their own config when they
figure it out.

-- 
Jonathan Gardner
gardner at sounddomain.com
(425)820-2244 x123


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«