On Montag, 25. April 2016 11:44:39 CEST Harald Sitter wrote: > On Mon, Apr 25, 2016 at 10:56 AM, Thomas Pfeiffer > > <thomas.pfeif...@kde.org> wrote: > > On Montag, 25. April 2016 07:58:04 CEST Luigi Toscano wrote: > >> Il 25 aprile 2016 03:40:33 CEST, Nick Shaforostoff <sha...@ukr.net> ha > > > > scritto: > >> >distro packagers note that libktorrent for kf5 conflicts with the one > >> >for kde4, which is needed for kget. > >> > > >> >kget for kf5 is in a semi-ported state now, and i wonder if anyone uses > >> >it at all. for example it has konqueror integration, but hey who uses > >> >konqueror nowadays? chromium, firefox and qupzilla (the most wayland > >> >friendly btw) have their own download managers. > >> > > >> >so i suggest either announce kget as being obsolete or finish its kf5 > >> >porting (i.e. find someone who could scratch his own itch doing that). > >> > >> Or why don't you make the new version of the library co-installable? > > > > Why? > > Either kget gets ported to KF5, or it's dead anyway. We should not > > tolerate > > applications hanging in a transition forever. > > FWIW, the library not being co-installable is kind of a bug, or at > least bad form anyway.
That is true, of course. The two things are probably orthogonal: Both libraries should be co- installable as long as both exist, but still we should not keep a kdelibs4- based KGet around indefinitely.
