- Debugger: Getting mixed signals
- 'Packaging Infrastructure' Contract Weekly Report #4
- Haiku monthly activity report - 06/2015
- 'Packaging Infrastructure' Contract Weekly Report #3
- 'Packaging Infrastructure' Contract Weekly Report #2
- GCI 2014 winners trip report (mentor side)
- TeX Live and LyX; Changes to the boot code
- 'Packaging Infrastructure' Contract Weekly Report #1
- Beginning of 'Packaging Infrastructure' Contract
- Haiku monthly activity report - 05/2015
'Packaging Infrastructure' Contract Weekly Report #4
After I took last week off for vacation, this week went very well. HaikuPorts has been migrated to GitHub, many corner cases related to HaikuPorter have been resolved, and most of the infrastructure issues that were directly related to setting up the package build server are gone.
HaikuPorts has, for the last few years, been living on Bitbucket. However, Bitbucket's integration with other services (e.g. Travis CI), overall interface, and code review system isn't as good as GitHub's. The concensus was already that moving to GitHub would be a good idea, so rather than having to do that later and write two integation systems in Haiku Kitchen (one for Bitbucket, one for GitHub), I opted to bite the bullet and do the migration now, rather than waiting. It took me all of Tuesday and most of Wednesday, but HaikuPorts is now fully migrated to GitHub. (You can find it here.)
(I also migrated the HaikuPorts mailing lists to FreeLists at the same time, you can find them here and here.)
With HaikuPorts migrated, I then set out to make use of the other bits of infrastructure GitHub provides, and to add more recipe linting capabilities to HaikuPorter so we can catch issues in recipes before they're sent to the build server. I set up Travis-CI so that all pull requests sent to HaikuPorts will be automatically checked for problems first, and once that was in place, moved on to HaikuPorter. I did a partial refactor of the linting system and cleaned up some bugs in there, set up COPYRIGHT linting, set up DESCRIPTION validation, made SUMMARY linting more strict, and made various other cleanups and consistency fixes in HaikuPorter and HaikuPorts.
I'm not working today, as it's a national holiday here in the U.S. (Fourth of July weekend), but on Monday I'll be resuming work on the buildserver.
See you all next time!
HaikuPorts has, for the last few years, been living on Bitbucket. However, Bitbucket's integration with other services (e.g. Travis CI), overall interface, and code review system isn't as good as GitHub's. The concensus was already that moving to GitHub would be a good idea, so rather than having to do that later and write two integation systems in Haiku Kitchen (one for Bitbucket, one for GitHub), I opted to bite the bullet and do the migration now, rather than waiting. It took me all of Tuesday and most of Wednesday, but HaikuPorts is now fully migrated to GitHub. (You can find it here.)
(I also migrated the HaikuPorts mailing lists to FreeLists at the same time, you can find them here and here.)
With HaikuPorts migrated, I then set out to make use of the other bits of infrastructure GitHub provides, and to add more recipe linting capabilities to HaikuPorter so we can catch issues in recipes before they're sent to the build server. I set up Travis-CI so that all pull requests sent to HaikuPorts will be automatically checked for problems first, and once that was in place, moved on to HaikuPorter. I did a partial refactor of the linting system and cleaned up some bugs in there, set up COPYRIGHT linting, set up DESCRIPTION validation, made SUMMARY linting more strict, and made various other cleanups and consistency fixes in HaikuPorter and HaikuPorts.
I'm not working today, as it's a national holiday here in the U.S. (Fourth of July weekend), but on Monday I'll be resuming work on the buildserver.
See you all next time!
- waddlesplash's blog
- Login or register to post comments

Comments
Re: 'Packaging Infrastructure' Contract Weekly Report #4
You can mirror or migrate Mercurial repositories very easily in a matter of minutes with hg-git. If you're only using Travis to lint then I really don't understand the migration.
Migrating before merging my pull request fills me with stop energy.
Re: 'Packaging Infrastructure' Contract Weekly Report #4
Also, your PR had merge conflicts on about 75% of the diffs, so it was impossible to merge anyway :/
Re: 'Packaging Infrastructure' Contract Weekly Report #4
Happy late 4th of July for you.
Re: 'Packaging Infrastructure' Contract Weekly Report #4
The main reason for leaving bitbucket for me is that their website is not doing well at all in any browser you can run from Haiku. Web+ will not render half of the elements on the page, and in Qupzilla you can't click on some buttons. Having to permanently switch between these two browsers to navigate haikuports was really annoying.
Github manages to work almost completely even with the NetSurf browser, which doesn't support Javascript. And they also provide the "hub" tool, so without a web browser available, you can still submit, review and merge pull requests.
Re: 'Packaging Infrastructure' Contract Weekly Report #4
Github doesn't work in any browser on haiku ATM. It may be better once the networking issues have been resolved, but right now, one has to use one browser to start a pr, and the other browser to submit it. This is a real pain.
Re: 'Packaging Infrastructure' Contract Weekly Report #4
I mentionned the "hub" tool for this reason. You can get it from haikudepot, then it becomes very easy to submit a pull request. From your ports directory do
. An editor will open, where you can enter your pull request message. That's it. No more messing with the web browser at all.