On Sunday 11 December 2011 23:37:28 Gravis wrote: > On Mon, 2011-12-12 at 10:13 +1000, Lindsay Mathieson wrote: > > On Sun, 11 Dec 2011 05:35:40 PM Gravis wrote: > > > konsole requires all these packages to be installed. > > > > Thats just a silly argument. Konsole does not exist in a vacuum, its a > > part of the kde desktop - all those dependencies are also shared with > > the vast majority of all the other KDE apps and have to be installed to > > have a functional kde install. > > From the ground up, installing the qt demos which include all the > functionality of Qt requires has 114 dependencies. However, to install > Konsole, requires 285 dependencies. > > Doesn't seem like a silly argument to me. Qt is just the framework which makes building the functionality of applications easier......so not every bit of functionality that an application has should wind up in Qt. The more uncommon or complex the application, the more non-qt components you will end up using. Konsole although it may seem simple enough from a UI perspective is actually quite a complicated application.
Dependencies are only an issue if the application doesn't actually 'depend' on them. If the application needs them to function correctly then it's better to have lots of smaller packges which only include that bit of functionality so that other applications don't also have to carry around / maintain the code in their application. Likewise if functionality is added to Qt it's self then more qt will need to become more modular so that applications can pick and choose which parts of qt to include.So you still have the deps, they are just called something else. Perhaps the question I should be asking is , what are you trying to achieve ? Are you trying to conserve disk space ? Do you feel the modularity making some particular task harder, if so what is it ? Andrew >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
