KDE-Forum.org

Although they are independent applications they are needed to keep the minimal desktop functional. As far as I know this is why they are needed (or at least why I undestand their are need).

KWrite and Konqueor textfile viewing use Kate embedable KPart. Kate KPart is part of the Kate library that is probably 95% of Kate so it's there to complete the 5%.

The control center at least needs to run things in superuser mode. I suppose that kdesu is there to do the job.

Well, if you see any "Print" menu entry somewhere in the desktop then you probably need kdeprint to do the job. It's not like "if you don't have a printer then no Print option is shown" (It would be nice though).

konsole, hmm, I think this is what puts "base" in "kdebase" ;-). Really I suppose that options like "Run in terminal window" have dependencies in konsole.

kpersonalizer is run once in the first session but its needed to have the KDE Desktop, as presented to the work, functioning and is a good thing for new users.

kscreensaver, well it probably could be left out but I think this is more or less like kdeprint. Control center allows to configure the screensaver, the desktop menu allows to configure the screen saver. I guess that its a given component of the system and not a plugin.

ksplash, how could you wait the kde startup without this little wast of memory and diskspace ;-). Is like kpersonalizer.

Well I din't mention kaddressbook because I really don't see why it's needed at kdebase but suppose that is something like kate. The library is needed somewhere and the whole app is cheap compared to the library only.

Well, I din't say anything usefull here, just my opinion so I would like to add one more thing.

I don't thing that this division of kdebase, pim, edu, etc is final. Things evolve do do dependencies. When everything works well, dependencies are perfected, meaning that commom parts a concentrated or in other way reused and all the components gain a more solid structure. Even the Qt framework is trying to work on their dependencies and separate UI from Qt core. So expect KDE to suffer similar changes.

Additonally to the reasons m4ktub mentioned you don't have to install those programs in case you don't want to.

Being in kdebase is purely a matter of source organisation, not packaging.
If you distibution has a good packaging paradigm it won't create one huge kdebase package which would force users to install full kdebase, but have small packages for parts of it.

I am quite confident that you can emerge only the applications and their dependencies you feel you'll need.
(Based on the fact that Debian can do this and Gentoo is usually as modular as Debian)

Cheers,
_

Quoted

Original von Amoeba

I was really just wondering why kdebase is packaged as it is.

You will have to ask your packager. KDE only creates arcives of the source files in a CVS module

Cheers,
_

Just to clarify
* katepart, kates editor component is in kdelibs.
* kdebase/kate is the kate and kwrite applictaions.

They are provided, because a Desktop needs a text editor. You could argue that the kate application could be in a seperate module, but something like kwrite is basic. But kde has a tradition for providing a full set of software.

Other comments:
KAddressbook is not in kdebase:
anders@pluto anders $ ls src/kde/kdebase/|grep address
anders@pluto anders $

Konsole is a very basic application, any GUI in a *nix environment requires a terminal application

kpersonalizer is required, it's used to help the user set up the environment.

ksplash is required, the splash screen is part of the kde desktop.

hm, this forum is unnice, i can't see the message i'm replying to... shame on the developers.

Quoted

Original von anders

hm, this forum is unnice, i can't see the message i'm replying to... shame on the developers.

The whole thread is accessible below the text input section. If you choose "Quote" rathern than "Reply" you even get the posting to reply to inside the message input area.

Cheers,
_