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

List:       kde-core-devel
Subject:    Re: KDE Platform Profiles
From:       Sune Vuorela <nospam () vuorela ! dk>
Date:       2010-04-26 8:18:35
Message-ID: slrnhtaj2r.nfa.nospam () sshway ! ssh ! pusling ! com
[Download RAW message or body]

On 2010-04-26, Kevin Ottens <ervin@kde.org> wrote:
> I'm just replying to that as I think maybe I've been unclear on this point.>  I 
> really meant about *binary packages* so at *runtime* maybe not all of kdeli> bs 
> is here. That's why it's really something related to how the packagers do 
> their job (to make sure a given app/lib has all its runtime dependencies in> 
> place).

Hi

I guess I should chime in here a bit.

It is a very large job to figure out for all kde apps which parts of
kdelibs&runtime (executables, kio slaves, kparts, and so on) requires.

I would suggest that it is the application maintainer who specify which
runtime components it needs. Maybe runtime components needed in 3
'levels'.

1) mandatory
2) optional, and normally installed by default
3) optional, and not installed by default

e.g. konqueror could specify that the khtml part, the http kioslave
and kbuildsycoca4 is in category 1, ftp kio slave in category 2 and
help kioslave in category 3.

If there isn't clear instructions from the application (and library)
developers, this is something that the packagers will get wrong more
than once.

It would also be nice if these instructions/guidelines from the
application maintainer was machine parsable (perl hashmap, xml, json,
yaml, ini-style, key:value email header style).

Then the packagers would have the required information, and they can
decide by them selves what to do about it.

/Sune

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