Hi, New weekly report via answer to Arne. This week wasn't the most productive I had. Mostly because of the ebuild work which take easily hours (yes, I should use ccache) and because of the summer and good weather. But, now, you can test my work and blame me, that should make everyone happy ! :)
Arne Babenhauserheide wrote: >> - configuration file update >> > In the means of "cfg-update -u" or similar? > [snip] > (sorry if I sound dumb, just want to be sure I didn't misunderstand) does > that > mean that you'll be adding the config updating stuff to packagekit, so we'll > have a cross-distro way of telling the package manager to update the configs? > Actually, this is going to be harder than excepted. Not technically speaking but it looks like people (backend/packagekit dev) want different things. So, in a first time, I'm going to show only a message about configuration files updated then I will take some time to discuss with devs and fix a specification. It looks like it will be an internal tool that will update configuration files but possible actions and how to interact have to be defined. So it will be a cross-distro way of updating configuration files. > Could you post the ebuild in here? > Good news is the ebuilds are now available in the gnome overlay. Why gnome overlay ? because they have polkit-0.93 and I needed the new polkit version. I've updated 0.5.1 version (last release) and live ebuild. 0.5.1 should be ok for testing now because the release wasn't done long ago and since I mostly worked on packagekit build system and ebuild. If you found issues, please, send me a private email or open a bug but better not flooding ml. > I wanted to test KPackageKit since I saw it in Kubuntu :) > > - http://www.kde-apps.org/content/show.php/KPackageKit?content=84745 > I'm going to write an ebuild for gnome-packagekit. It's surely the best way to test packagekit because it's developed by the same guy. If anyone wants a KPackageKit ebuild, I can help but not write it. > I don't know if I'll manage to grab enough time to do real testing, but I'll > try. > Even small feedbacks are welcome ;) PackageKit should be tested with a GUI but as I have not released a gnome-packagekit ebuild, you have two ways to test it: - use pkcon which is a CLI client to packagekit but really basic like if you want to install foo package, it will install it and dependencies without telling you if you accept them. For 'atomic' tests, it's the best way of doing. - build yourself gnome-packagekit shouldn't be hard at all ;) So, this week, I will add a ACCEPT_PROPERTIES feature to portage. I was thinking of filtering interactive PROPERTIES in my backend but zac told me he was planning to add this feature. It should be available soon (one or two days) and the gnome-packagekit ebuild will be the next step. So, you should have it in two or three days. Depends on the difficulty. If the build system is clean as the PackageKit one was, it will be hard and I've no commit access to gnome-packagekit unfortunately. Thanks, Mounir
