[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: organizing kdebase
From:       Josef Spillner <spillner () kde ! org>
Date:       2007-02-23 8:10:42
Message-ID: 200702230910.43907.spillner () kde ! org
[Download RAW message or body]

Am Donnerstag, 22. Februar 2007 12:43 schrieb Benjamin Meyer:
> > knewstuff (generic app for grabbing knewstuff data; might really be more
> > suited to kdeutils or even extragear to be honest)
>
> If it requires input and can't stand alone then it would go in runtime
> otherwise if it is a stand alone app then workspace (a core feature of
> KDE4?) or kdeutils.

The 'khotnewstuff' standalone executable is of somewhat limited use right now 
since it can download arbitrary data but cannot properly (un)install it - 
which is no wonder given that a lot of the higher-level installation logic is 
part of the applications. We could move more of that into declarative 
descriptions (the upcoming *.knsrc files), but that's really up to the app 
maintainers, to give input what features they want to see.

Since knewstuff2 will enter kdelibs in a few mondays, I wonder what to do 
about the runtime. There is some code which needs a central place, such as 
installation lockdowns (which should be somewhat integrated with kiosk), 
although this code could potentiall go into kcontrol.
I haven't followed development of kdebase recently and I'm not aware of any 
requirements for khotnewstuff to be in kdebase, so moving it to kdeutils or 
elsewhere seems ok. Please leave it in kdebase until knewstuff2 comes in 
though.

Josef
[prev in list] [next in list] [prev in thread] [next in thread]