CVS support in KDE

Neil Stevens neil at qualityassistant.com
Sun Jan 19 17:40:29 GMT 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday January 17, 2003 06:06, Carsten Pfeiffer wrote:
> On Friday 17 January 2003 14:57, Adriaan de Groot wrote:
> > Count the number of different CVS modules in that list. kdevelop,
> > kdesdk, and quanta at the very least, kdebase for kate. Now, where
> > does the factored-out code go? Not in base, since you can't demand a
> > quanta user to have kdebase, can you. Not in sdk, since that gives you
> > even worse dependencies. So that leaves either libs or "elsewhere".
> > Make sure it is clear _where_ the shared code is going to live before
> > you start, and where the apps are going to end up.
>
> 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.

Plus, if this is done with a generic enough interface, it could support 
systems other than cvs.

- -- 
Neil Stevens - neil at qualityassistant.com
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+KuMNf7mnligQOmERAnRhAJ9VXdBE76aGEDE7q5yPDqr4kg2Y4ACfQL9C
ZFDcD4h6HXGi1vfBgZcO0GM=
=3y4u
-----END PGP SIGNATURE-----





More information about the kde-core-devel mailing list