The past week I’ve finished the muon package, available @ git.debian.org/?p=pkg-kde/kde-extras/muon.git on the gsoc-floris-2014 branch (use at your own risk!)
Also, I’ve finished up the KAuth support when adding/removing repos (already pushed to the master of Muon). Most importantly, I’ve started integrating apt-listbugs a most important component of Debian. What does this mean and how it will affect the end-user? Well, having apt-listbugs integrated means that the user will be warned when installing packages if the packages have some serious/grave/critical bugs!
I am still working on making it async and I hope to be done by tonight. Also, some formatting work on the dialog is still needed. Check it out bellow:
After I finish the apt-listbugs integration, I will get started on writing up some apt unit tests as suggested by Aleix. Also, I will work with Sune on updating the qapt package as well.
In a nutshell:
*KAuth support implemented
*initial apt-listbugs integration
Plans for next week:
*finish apt-listbugs integration (async, with pretty formatting!)
*apt unit tests
*update qapt package
Thanks for reading, see you next week!
This has been a terrific week and a real learning experience for me. I finished packaging both Muon and QApt for Debian; my first two real debian packages, with very different packaging styles! Sune (svuorela), Maximiliano (maxy) and others helped me allot to understand the tools and I thank them very much for their support.
While the first part of this second week was all about trying to make a solid package, the second part was me figuring out Policykit and KAuth in order for us to let go (as much as possible) of Kdesudo. I have managed to do a complete turnaround from kdesudo through policykit and now I am working on making an add-repo helper in C++/Qt using KAuth to keep it in line with QApt, in order to have a more uniform codebase. Big thanks to Aleix (apol) that guided me through the different uses of policykit and Kauth.
To keep it short, policykit will not be used directly except QApt, in every other case we’ll use KAuth. I’m very close to finishing the KAuth add-repo helper and that will add improved functionality, as it extends well in what I will be doing next: renouncing specific backend support; The helper will manage how backends add/remove repos, meaning that if you use PackageKit you will no longer be tied to Apt if you want to use Muon!
Here is a screenshot of the configure-software button in muon-discovery (finally) working on Debian and launching software-properties-kde:
And below are some screens of Muon in the wild, running on Debian:
Auth required through policykit
I hope you enjoyed this update and stay tuned for the debian package which is currently under review.
My name is Floris (FlowRiser) and during GSoC I will be working at the project “Getting Muon ready”. I am guided by two awesome mentors: Sune Vuorela (svuorela) and Aleix Pol (apol). Essentially what we are trying to accomplish is not only port Muon to Debian, but also make it part of Debian; making users that use and love Debian confortable with it. Some of our goals are: integrating apt-listbugs into muon, making installing updates easier and contributing to both KDE and Debian at the same time.
The exact plan (week by week), subject to change is here: https://wiki.debian.org/SummerOfCode2014/StudentApplications/FlorisAndreiStoicaMarcu.
This week, we focused on getting the core functionality of Muon for Debian; Browsing packages, installing/updating, getting update notifications; Today I will also be making some packaging work, so that other people can begin testing Muon.
The exact changes so far:
*changes to the .desktop files parsing, so you can browse packages as expected
*changes to the way more than one backend interract
*created a new releasechecker script for future use
Plans for next week include:
*fixing kdesudo use
*fixing use of specific backend resources