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

List:       kde-core-devel
Subject:    Re: organizing kdebase
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2007-02-23 9:08:32
Message-ID: 200702231008.32370.schumacher () kde ! org
[Download RAW message or body]

On Thursday 22 February 2007 17:43, Aaron J. Seigo wrote:
>
> however, i didn't consider scripts a reason to put something into runtime/,
> which i kept specifically for application software (which can be written in
> python, ruby, etc.. but that's not a "script" in my mind). scripts can
> depend on kdebase/?

This distinction between "applications" and "scripts" sounds a bit artificial 
to me. Both are KDE applications in the sense that they use the KDE 
infrastructure to fulfill a task for the user.

I see why you see a difference there, but expressing this through dependencies 
by putting them in a separately installed package or in a special area in SVN 
seems to be too fine granular to me.

So I think it's fine to put them into runtime. We could put them into an own 
subdirectory there to express that they are different than other parts of the 
runtime, though.

-- 
Cornelius Schumacher <schumacher@kde.org>
[prev in list] [next in list] [prev in thread] [next in thread]