This article is a summary of all the changes made on Automated Gentoo System Updater project during week 2 of GSoC.

Project is hosted on Github

Progress on Week 2

This week was all about packaging and testing. The updater is still in its infancy, but it’s much better to package everything nicely right away and not think about this in the future.

I kicked things off by bundling all the code into one directory and set it up as a Python module. Then, with some automation magic I whipped up a Github Actions workflow that takes care of publishing the package to PyPI. The idea was to make it installable using pip.

But to my surprise it turns out Python pip had it’s permissions in OS severely limited after some recent changes. To get the package to install on the system, it demands the ‘–break-system-packages’ flag. This doesn’t look very user friendly 😅.

So, I took a different route and crafted an ebuild instead, which I’ve shipped off to the GURU repository. It’s already on the main branch and is available for installation on Gentoo!

Apart from packaging I also penned some unit tests for the main Python file and did more testing in Docker containers and VMs.


The hardest part undoubtedly was writing an ebuild. On paper it sounds very straightforward - ebuild is just a file that tells Portage how to install the program on Gentoo. In practice, however, it’s not as easy as it sounds.

First of all, a local repository needs to be set up to test it properly, I’ve covered it here.

Secondly, it’s very confusing how to account for all dependencies. My script uses Python, Bash and also requires some system packages, all of which have their own dependencies. In the end, I settled on packaging Python and Bash files into a Python module, and then only specify dependencies for this module and additional OS packages in the ebuild.

Thirdly, after the ebuild is ready and tested it actually needs to be pushed to GURU repository. This part also can be tricky because commits need to be signed by a GPG key, and if there are any problems in the ebuild you will get emails from Tinderbox - Gentoo’s CI and QA system, which catches all your ebuild mistakes and aggressively tells you about them.

Writing unit tests is also very tricky. Not only that, it also seems useless and unnecessary. For me, if the script passed all the test in Docker container then there is no need to write unit tests. However, I should also note that my Docker tests are not automated and don’t cover much of the functionality, so probably I should focus more on writing unit tests….

Plans for Week 3

The updater’s output currently is too messy and it’s all over the place. Time to tidy that up!

An important part of the project is the parser that will read and understand logs from emerge. I plan to start coding the parser next week.

And almost forgot – I need to learn how to post blogs on Gentoo’s website and post a project announcement on it. I think gentoo_update is ready to get some more attention and user feedback.