On Fri, Apr 14, 2017 at 11:20 AM, Rüdiger Meier
On 04/14/2017 04:07 PM, Luca Beltrame wrote:
Il giorno Fri, 14 Apr 2017 15:19:54 +0200 Rüdiger Meier
ha scritto: Moreover if ktorrent and other mentioned programs would be developed independently then one could just easily try out a newer (probably
You *can* do that already. You don't need to install Plasma to run ktorrent.
And they're developed independently. In particular, ktorrent is part of the "extragear" group of applications, meaning that they have their own release schedule and their own pace of development. They have no ties with either Frameworks, Plasma, or Applications.
I've just tried for fun to install ktorrent and gave up after 30 minutes. I don't think there is a way to install it without many other deps from the kde project. There is no documentation about what dependencies are needed. I can only run cmake again and again, downloading and installing more and more deps from KDE and hoping that finally it would not complain anymore. I'd say it does not look like ktorrent is made for users who simply wants to install a torrent client quickly.
Maybe people who are familiar with the KDE tree like you may manage this faster than me, for me it's too painful.
The dependencies are listed in CMakeLists.txt, and they all seem like pretty straightforward things that something like ktorrent would need. But when it comes to building from source, generally it is easier to use kdesrc-build, which handles all of that for you. GNOME has something similar called Jhbuild. Lots of projects have similar tools to make dependency handling easier. This isn't a particular issue with KDE, any useful piece of software will require multiple dependencies. I don't see why you think projects that are part of the KDE community are particularly bad in this regard. On the contrary, a lot of work has been going on to limit the dependencies of KDE software to only what is really needed.
Other examples include yakuake, konversation, labplot...
Haven't checked them but I know also two good examples qcachegrind and troijta which have no kde but only Qt deps. Still the fact that they are hosted on kde.org makes them suspect to me (the "trust" thing). I'm using qcachegrind (no alternative) but I would not use troijta, since it was moved to KDE in 2012.
So you are saying you explicitly distrust anything and everything that is part of the KDE community, merely based on the fact that they choose to associate with that community? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org