CVS support in KDE

Carsten Pfeiffer carpdjih at
Fri Jan 17 15:26:22 GMT 2003


On Friday 17 January 2003 15:22, Adriaan de Groot wrote:
> On Fri, 17 Jan 2003, Carsten Pfeiffer wrote:
> > Please -- we've had enough boring discussions of where to put shared code
> > already. If many applications are going to use it, it's going to be
> > kdelibs. If there may be different implementations, we have
> > kdelibs/interfaces.
> Damn right they were boring and tedious, but I must have missed the
> conclusion that says that shared code goes into libs.
> Your statement implies that the move of KMail to kdepim is not needed,
> because we can factor out the _build-time_ shared code into kdelibs.

KMail is not generally useful to all KDE applications, while CVS support is. 
We won't clutter up kdelibs to satisfy built-time application dependencies. 
kdelibs contains code that is generally useful to many applications.

> Also, the IOSlaves discussion ended up with Coolo saying [paraphrase]
> "IOSlaves in kdelibs? No way." So this _run-time_ shared code must be
> somewhere else.

Yes. Same with kdelibs/interfaces. You can compile applications against those 
interfaces, but you don't know who's providing the implementation. E.g. the 
regexp-editor is in kdeutils. Using that interface, you need kdelibs at 
build-time, but at runtime you either install kdeutils or you will get an 

> I'd be as glad as anyone if there was a clear decision on this issue (both
> run-time  and build-time) and I'm not trying to reopen the discussion. I
> just want to know what the decision is. And if your say-so is binding, or
> if you are stating a decision that was reached and that I missed, fine. I
> will follow the rules.

I'm not a decision maker, but I don't see the point of starting a discussion 
of where to put code before we have code at all.

Carsten Pfeiffer


More information about the kde-core-devel mailing list