Starting out with a question

[Carlos Leonhard Woelz]

On Wed,  3 Mar 2004 21:06:01 +0100, "Joost De Cock"
<joost.decock at astrid.be> said:
> Hi there,
> 
> my new year's resolution for this year was to (finally) get involved in a
> FOSS
> project but I never really could decide what to pick. With the launch of
> kde-quality I think I'll stop making excuses and sign up for the ride.

Welcome.

> I'm not a programmer but I know how to do it. I just never got into the
> OO
> stuff. If possible, I'd like to become a KDE god ;) It happens that I
> ordered
> the QT book a couple of days ago (pure coincidence) since I wanted to
> learn KDE
> programming anyway.
> I really like KDE-Pim, I'm a Kmail en Kitchensync addict, so I'd really
> like to
> help out those projects.

I am not a programmer myself, therefore I can assure you this does not
prevent someone to be higly productive immediately. If you are a newbie
programmer, there are many activities where you can perform to learn and
contribute at the same time. Adriaan de Groot is the guy to contact for
newbie developer PIM activities. Or if you have general programming
questions, I am sure Alexander Neundorf, who is subscribed yo this list,
can help you out.

> However, I have one question. This whole 'CVS unstable branch' thing is
> new to
> me. I'm not afraid to run bleeding edge code, but I use Debian unstable,
> and I
> was wondering if that requires some special configuration?

The KDE building guide was designed to permit the co-existence of your
distribution (in the case Debian) and an unstable KDE build. If you are
planning to work with KDE PIM, you have the following options:
1) You can build KDE unstable.
1) You can build KDE stable and only KDE PIM unstable
2) You can build only the KDE PIM unstable module over KDE 3.2, if you
installed the KDE 3.2 debian packages. This option is not covered in the
building guide, I did not try it. It is easy to do that if you compile
KDE PIM as root, but it is not a very clean solution. If you compile it
and install it as an user, but the rest of KDE is installed as root in
another dir, I am not sure it will work. But I am saying too much and
probably scaring you more than helping :) I would go with 2, the guide
explains it in detail.

To build KDE, you don't need special configuration, you have to install
several development packages. The guide explains more.

> Could you point me to some more info on that matter.

Sure, the step by step guide is here:

http://quality.kde.org/develop/cvsguide/

Cheers,
-- 
  Carlos Leonhard Woelz
  carloswoelz at imap-mail.com

-- 
http://www.fastmail.fm - A fast, anti-spam email service.