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

List:       kde-devel
Subject:    Re: mark kget obsolete?
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2016-04-25 9:04:26
Message-ID: 18503782.iOUVJu6p1F () whitebase ! usersys ! redhat ! com
[Download RAW message or body]

On Monday 25 of April 2016 10:56:03 Thomas Pfeiffer wrote:
> On Montag, 25. April 2016 07:58:04 CEST Luigi Toscano wrote:
> > Il 25 aprile 2016 03:40:33 CEST, Nick Shaforostoff <shafff@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.

What is the cost for making the library co-installable? We are debating for 
something more than it takes to have it fixed. If kget should go away at some 
point with other unported applications, but no need to kill it when we are 
still transitioning (because we are still).

-- 
Luigi

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