Why modules? (was: Re: A humble packager's request: Retire kdeaddons.)

[Russell Miller]

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

On Wednesday 11 February 2004 10:08, Benoit Walter wrote:

> The weather kontact plugin should be at the same place as KWeather. I have
> seen many people wonder why the plugin does not work... But KWeather is in
> kdetoys.
> I personnally think it would make sense to move all optional kontact
> plugins to kdeaddons/kontact/plugins...

OK I'm going to think outside the box here, and this suggestion may indeed be 
stupid (or at the least impractical), but I hope that it will start us on the 
road to a little more creative thinking:

Why do we have modules at all?  It seems to me that, except for perhaps KEG 
and the new kdesupport, we could squish them all into one and use configure 
checks to decide what parts to build and install.  All this separate module 
stuff seems to be causing a lot more trouble than it's solving.

This would remove dependency problems, remove squabbles over where to put 
particular software packages, and solve the problem of duplicate compiles 
(each program would be able to build the dependencies that it needs).

We can always use namespaces to isolate globals as required...

I've expressed that I realize that this may be a bit too far for most peoples' 
comfort, but please restrict criticisms to fact.

- --Russell

- -- 
10:16:08 up 3 days, 22:58, 1 user, load average: 0.15, 0.34, 0.31

Russell Miller - rmiller at duskglow.com - Somewhere near Sioux City, IA.
Youth cannot know age, but age is guilty if it forgets youth
    - Professor Dumbledore
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAKlYwURTA4VCI9OARAuN5AJ9HmU0kZTZTLRn2D8bNk21sYZ4o7gCeMemh
OfuTf+a+W7FGxRH92YCKA40=
=JTEm
-----END PGP SIGNATURE-----