Moving KMail, KNode, Korn and related libraries to kdepim
cap at capsi.com
Tue Jan 14 20:47:19 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Tuesday January 14 2003 9:35 pm, Dirk Mueller wrote:
> so before we move it around yet another time, let me suggest to create a
> separate module for them. We can then map the directories into any module
> we want at a fixed, minimal cost. We should have done that years ago.
> The same probably applies to kmail, which could very well be its own
> toplevel module with all its branches nowadays.
I wouldn't like a situation like GNOME which seems to have a seperate module
for almost everything, but I would support seperating KMail.
Splitting off the kioslaves.. if kdelibs will depend on that (and it will have
to for http, unless you're only talking about the mail related slaves), I
would prefer to just put them in there. But I wouldn't really object a split.
The impact on end users shouldn't be too hard and if it suits those who
actually develop the slaves, good for them.
Rob Kaper | Gimme some love, gimme some skin,
cap at capsi.com | if we ain't got that then we ain't got much
www.capsi.com | and we ain't got nothing, nothing! -- "Nothing" by A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel