'Packaging Infrastructure' Contract Report #5
It’s been two weeks since my last report, as I wasn’t working full-time these past two due to some outside appointments and other conflicts. I’ll be back to working full-time next week. Despite this, I managed to make a lot of progress on a number of fronts.
As mentioned previously, the next thing to work on in the build server was file transfers. These are now complete, and the build server is now capable of handling file transfers from the client to the server. This is a crucial feature, and it needs to work well, as essentially the whole function of the server revolves around transferring packages from the client to the server so they can be distributed. It took a bit of trial and error, but it now works well, and the transferred files pass checksum tests. All of the transfers occur over TLS, so integrity and security is ensured as well.
Since I crossed the halfway point in the contract, I submitted an invoice to Haiku Inc. for the first half. Ryan Leavengood took the time to review the code I was writing and give suggestions on what to improve. I spent yesterday working on a lot of his suggested cleanups, and the code is significantly more understandable to others as a result.
On the HaikuPorts front, I made some more progress in cleaning up HaikuPorter. At this point, there’s not much else to do without a full refactor, and it’s solid enough that running it on unattended build machines is probably fine. Most of my efforts here were focused on linting, as it’s best if more problems can be caught before the build even starts, rather than try and handle a contingency after the build has already started (as there might be multiple machines working on a build of a set of packages at once.)
Next week, I’ll work on dependency solving, and HPKG repository management. This will enable Haiku Kitchen to detect when packages are out-of-date with the recipes, automatically rebuild them, and generate the HPKR file needed for
pkgman and friends to be able to install them.
- Haiku monthly activity report - 06/2019
- Coding week no 2 and 3
- [GSoC 2019] Weeks #1, #2 and #3 progress reports
- Haiku monthly activity report, May 2019
- Coding week #1
- Mid Community Bonding--Progress
- Haiku to mentor 3 interns in Outreachy and GSoC
- Introducing myself gsoc 2019
- [GSoC 2019] Improving the btrfs filesystem
- Haiku monthly activity report - 03 and 04/2019