Re: Final kde-runtime splitting plan
On Tuesday 25 March 2014 23:01:39 Luigi Toscano wrote: Àlex Fiestas ha scritto: Hi there Today Aleix and I are starting to split kde-runtime so we have gone through all the components again making sure that everything has a suitable destination. The result is this [1] wiki. Please, check that you are ok with the destination of each component and also check the things that have been targeted as **REMOVE** should be really removed (we believe so). Why kreadconfig (which includes kreadconfig and kwriteconfig) is going to be in plasma-workspace? Isn't it useful for every KConfig-based component/application? Maybe kde cli tools could be the target... Yes, but only assuming that kde-workspace can then depend on kde-cli-tools at runtime (since startkde uses kreadconfig). -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Final kde-runtime splitting plan
On Tuesday 25 March 2014 20:00:51 Albert Astals Cid wrote: Can you give a rationale of why we're removing the following things? kfile4 kfile4 is only useful to test a library that is right now on kde4support. Maybe we can move it there if you want. kio_cgi Who needs to execute a cgi script without a web server? If you do then we can move it its own repo, I really don't want to see distributions shipping this kio in a package such of kioslaves-extras since it really doesn't offer anything useful for most of our user base. kio settings Browsing the settings in the file browser does not seem like a really convenient thing to have, and of course it adds more code to maintain. If you want to keep it that's fine but then please become maintainer and tell us where to move it (maybe kioslave-extra?). Cheers! signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Final kde-runtime splitting plan
On Tuesday 25 March 2014 23:01:39 Luigi Toscano wrote: Why kreadconfig (which includes kreadconfig and kwriteconfig) is going to be in plasma-workspace? Isn't it useful for every KConfig-based component/application? Maybe kde cli tools could be the target... I thought there was another tool to do such things but apparently there are not, so yes we have to move kread/write config elsewhere. I wonder if a good place will be kconfig itself? they are useful tools for any kconfig user. Maintainer, any thoughts? signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Final kde-runtime splitting plan
On Wed, Mar 26, 2014 at 10:02 PM, Albert Astals Cid aa...@kde.org wrote: El Dimecres, 26 de març de 2014, a les 11:42:01, Àlex Fiestas va escriure: On Tuesday 25 March 2014 20:00:51 Albert Astals Cid wrote: Can you give a rationale of why we're removing the following things? kfile4 kfile4 is only useful to test a library that is right now on kde4support. Maybe we can move it there if you want. Wouldn't hurt. What do others think? Personally I think that in its state it's not an end-user tool but more of a tool to test Nepomuk. I would rather see new tooling coming from Baloo and the new tools rather than doing acrobatics to keep it alive. If somebody has a non-abstract reason, I would be fine with moving it to kde4support. kio_cgi Who needs to execute a cgi script without a web server? If you do then we can move it its own repo, I really don't want to see distributions shipping this kio in a package such of kioslaves-extras since it really doesn't offer anything useful for most of our user base. Well you can't know it offers anything useful, and at the end it's a few lines of code that doesn't seem to need lots of maintainance, so why kill them? kio settings Browsing the settings in the file browser does not seem like a really convenient thing to have, and of course it adds more code to maintain. If you want to keep it that's fine but then please become maintainer and tell us where to move it (maybe kioslave-extra?). Same as kio_cgi, I don't see why you want to kill something that works and that you have no objective way to know if people are using or not. I would move those two to kioslave-extra. Shouldn't be much work anyway. Cheers, Albert Cheers! ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel Aleix ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Final kde-runtime splitting plan
On Wed, Mar 26, 2014 at 12:37 PM, Carlos De Maine car...@demaine.orgwrote: On Wed, 26 Mar 2014 11:28:24 AM Àlex Fiestas wrote: On Wednesday 26 March 2014 09:52:08 Carlos De Maine wrote: On Tue, 25 Mar 2014 04:18:22 PM Àlex Fiestas wrote: Hi there Today Aleix and I are starting to split kde-runtime so we have gone through all the components again making sure that everything has a suitable destination. The result is this [1] wiki. Please, check that you are ok with the destination of each component and also check the things that have been targeted as **REMOVE** should be really removed (we believe so). Kio-network works on 4.13 for me. http://wstaw.org/w/2ADU/[1] Does have a weird issue that it has to be refreshed twice to show any content for the first time, but works perfectly after that. Would be a pity to remove the only network browser. You can't actually execute anything from it can you? It is basically a browser that lets you list things but little more which is quite useless imho. I'm good on moving it elsewhere but what I would like to avoid is shipping this not finished kio as part of the official release which servers only a use (browser and discovery) that most people do not need by itself. It opens fish/sftp, smb, afc kioslaves in dolphin, launches krdc for rfb and vnc, opens konsole (at password entry stage) for ssh. In the past when the upnp kioslave was still compiling i was able to access my upnp shares around the network as well. I agree its not fully functional but in it's present state it is still incredibly useful in the file dialog for accessing the network transparency of kde's kioslaves. With a bit of polish (such as linking ktp to *.presence, fish kioslave for *.udisks-ssh) it would be perfect. Cheers Cheers. It is a pity indeed. I just tried it myself on KDE4 and it seems like it wants to work but it doesn't quite. I wouldn't want this to prolongue, this project couldn't go through kdereview at the moment successfully, so there's little reason for it to stay in. Instead of removing, we can put it differently and move it to a little farm where kioslaves go die, but if somebody doesn't commit to it, it has to go. Also there's many other kioslaves in need for love: ** Adopt your kioslave ** Aleix ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Final kde-runtime splitting plan
Hi there Today Aleix and I are starting to split kde-runtime so we have gone through all the components again making sure that everything has a suitable destination. The result is this [1] wiki. Please, check that you are ok with the destination of each component and also check the things that have been targeted as **REMOVE** should be really removed (we believe so). Cheers ! [1] http://community.kde.org/Frameworks/Epics/New_Runtime_Organization signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Final kde-runtime splitting plan
El Dimarts, 25 de març de 2014, a les 16:18:22, Àlex Fiestas va escriure: Hi there Today Aleix and I are starting to split kde-runtime so we have gone through all the components again making sure that everything has a suitable destination. The result is this [1] wiki. Please, check that you are ok with the destination of each component and also check the things that have been targeted as **REMOVE** should be really removed (we believe so). Can you give a rationale of why we're removing the following things? kfile4 kio_cgi kio settings Cheers, Albert Cheers ! [1] http://community.kde.org/Frameworks/Epics/New_Runtime_Organization ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Final kde-runtime splitting plan
Àlex Fiestas ha scritto: Hi there Today Aleix and I are starting to split kde-runtime so we have gone through all the components again making sure that everything has a suitable destination. The result is this [1] wiki. Please, check that you are ok with the destination of each component and also check the things that have been targeted as **REMOVE** should be really removed (we believe so). Why kreadconfig (which includes kreadconfig and kwriteconfig) is going to be in plasma-workspace? Isn't it useful for every KConfig-based component/application? Maybe kde cli tools could be the target... Ciao -- Luigi ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
