tag:blogger.com,1999:blog-7523589.post3668944009898320382..comments2024-02-20T19:17:55.835+01:00Comments on TSDgeos' blog: My KDE Onboarding Sprint 2019 reportAlbert Astals Cidhttp://www.blogger.com/profile/12001470108926138921noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7523589.post-9447554621300477492019-07-29T22:10:11.660+02:002019-07-29T22:10:11.660+02:00@Dan yes i know for PIM you have a docker image, t...@Dan yes i know for PIM you have a docker image, talk to Volker he was there on the sprint and he agreed that isn't the solution.<br /><br />Also, no idea why you say Okular is simple, you have to build gs to make it work ;)<br /><br />As far as I understand there's flatpak ways of not having to rebuild everything all the time. <br /><br />@Jan yes, i've tried Gnome Builder, it's easier to use, problem is, it's also a bit more useless since it only works as "flatpak builder", not as a regular IDE like KDevelop.Albert Astals Cidhttps://www.blogger.com/profile/12001470108926138921noreply@blogger.comtag:blogger.com,1999:blog-7523589.post-53925454422506642282019-07-29T16:28:46.148+02:002019-07-29T16:28:46.148+02:00Usually if people are fixing applications, the app...Usually if people are fixing applications, the app is listed at the end of the manifest (after the dependencies), which means only the app needs to be rebuild. But you are right that if you end up fixing issues deep down in the dependency chain, you can end up building everything over and over, which is not a good experience either.Honza Grulichhttps://www.blogger.com/profile/00894385382360621241noreply@blogger.comtag:blogger.com,1999:blog-7523589.post-32371314584410089392019-07-29T16:16:04.594+02:002019-07-29T16:16:04.594+02:00Flatpak for development really only works if you h...Flatpak for development really only works if you have a simple app like Okular or Dolphin. It becomes annoying when the Flatpak'ed app bundles additional dependencies, because once you touch one of the dependencies, Flatpak will rebuild everything - using Flatpak for KDE PIM development for instance is not doable at all, since if you touch e.g. KIMAP library just to fix a small bug, you would have to wait for ages for Flatpak to recompile everything that's listed below KIMAP in the manifest file (which is a *lot* of things :-)). Same would likely go for Plasma (if that can even be Flatpak'ed).<br /><br />For PIM we have a dedicated Docker image, which contains the latest Frameworks (from Neon nightly), pre-configured kdesrc-build, ccache, the environment variables are all set up, it even has KDevelop and QtCreator installed inside and there are some additional shell scripts (build.sh, run.sh) to make it easy-to-use even for people without any Docker knowledge. If you need newer Frameworks you just rebuild the image. I find that more flexible than Flatpak for development, since it's basically the same as developing on your system, but everything is sandboxed inside the container - although I have to admit I doubt that you could print from Okular inside the container either :)dvratilhttps://dvratil.cznoreply@blogger.comtag:blogger.com,1999:blog-7523589.post-91248412870758742712019-07-29T09:27:12.512+02:002019-07-29T09:27:12.512+02:00Like you said, I'm afraid that until we collec...Like you said, I'm afraid that until we collectively say "Let's do it" we won't see any major progress or contribution from other people in the Flatpak adoption. There is lot of work which cannot be done in just few people (like it was until now, me working on the portals in Plasma and Qt, Aleix pushing the KDE runtime and Discover and you pushing the apps on Flathub). Also many apps need to be properly tested and changes need to be made to make them fully work in Flatpak without any limitations. All the work is totally worth it, there is a huge potential in Flatpak and it will make life much easier for new contributors, especially if we have better integration in KDevelop. Have you seen gnome-builder in action? From what I remember, you pick an app, it already provides Flatpak manifest and you can do all the changes you want and simply build it and test it, without messing with your system or thinking about dependencies. Honza Grulichhttps://www.blogger.com/profile/00894385382360621241noreply@blogger.com