Building packages with haikuporter
HaikuPorter is a python tool that takes a so-called recipe that describes the dependencies of a software and how to download, build and package it.
The HaikuPorts Wiki has all the info to get started writing recipes. But it gets into too much detail if all you want is use HaikuPorter to build stuff with existing working recipes.
Here’s a quick step-by-step guide how to do that.
1. Getting HaikuPorter and the Recipes
Get the HaikuPorter tool and the haikuports tree with all the recipes:
git clone https://github.com/haikuports/haikuporter.git --depth=50 git clone https://github.com/haikuports/haikuports.git --depth=50
That'll create two directories: "haikuporter" with the python tool and "haikuports" with all the recipes categorized in sub-folders.
--depth=50 limits the cloning to the last 50 commits to save download time and disk space.
2. Setting up HaikuPorter
Put HaikuPorter into the system's “Path”, so it can be invoked like any other command:
cd haikuporter ln -s haikuporter ~/config/non-packaged/bin/
Copy and edit the haikuports configuration file:
cp haikuports-sample.conf ~/config/settings/haikuports.conf lpe ~/config/settings/haikuports.conf
In the haikuports.conf file you have to edit/un-comment the lines:
- TREE_PATH - where you cloned the haikuports tree, e.g. "/boot/home/haikuports"
- PACKAGER - your name and email address, e.g. "
This is for running the official 32bit Haiku (gcc2hybrid), where the older gcc2 compiler is the default to maintain BeOS compatibility and "x86" is a modern compiler (currently gcc5.4) for applications that won't build with the ancient gcc2.
3. Using HaikuPorter
Now you can start using HaikuPorter. You get all its options with "
In the haikuports tree, you search the recipe of the software you’d like to build. You can also use, e.g. "
haikuporter -o artpaint" to have haikuporter look for a specific recipe, here for “ArtPaint”.
To build ArtPaint, you type:
haikuporter -S -j4 --get-dependencies --no-source-packages artpaint
-S : enforce "strict policy" to create standard compliant HPKGs.
-j4 : use 4 cores when building to save time.
--get-dependencies : automatically download all packages needed for building that aren’t already installed.
--no-source-packages : don’t create a package with the source code.
artpaint : build the latest recipe for "ArtPaint".
You find successfully built packages in the folder "
4. Keeping uptodate
The haikuports tree receives almost daily changes with new, updated and fixed recipes. To stay abreast with those changes, you should regularly update. This is very easy with "
Likewise, haikuporter itself gets updated from time to time. At the latest if recipes start to fail building, you should update. This, too, is quite easy; you enter the directory "haikuporter" that you have cloned in the 1st step and use
git to pull in all changes:
cd haikuporter git pull
5. Tips & Tricks
To save yourself much typing, you can add this line to the file ~/config/settings/profile (a text file that you have to create if it doesn’t exist already):
alias hp='haikuporter -S -j4 --get-dependencies --no-source-packages'
Now you can build with a simple "
hp artpaint" and have those standard parameters added automatically.
Some software can’t be built with gcc2 and needs the modern compiler. You can see that in the recipes that declare:
ARCHITECTURES="!x86_gcc2 x86 x86_64" SECONDARY_ARCHITECTURES="x86"
The "!" says the package can't be built for that architecture. A "?" shows that it hasn't been tested for it.
In such a case, haikuporter will complain that "it is broken on the target architecture". You instruct haikuporter to build with the secondary architecture by appending a "
_x86" to the recipe name, e.g. "
Sometimes you find recipes for different versions of a software. HaikuPorter builds the latest by default. If you'd like a specific version, you can append the version number found in the recipe's filename, e.g. "
bepdf_x86-2.0.0" to build v2.0.0 of BePDF for the secondary architecture (gcc5.4 currently).
If something goes wrong and you want a fresh start, open the folder of the recipe you try to build and delete all folders starting with "
work-". Also delete the "
download" folder if you suspect a corrupted source archive.
Do a "
haikuporter artpaint -c" for ArtPaint as example. In some weird cases you may have to also delete the folders "
haikuports/packages" and "
haikuports/repositories", which will be time-consumingly recreated with the next build.
- [GSoC 2018] TrackGit - Git Addon for Tracker
- Haiku monthly activity report - 03/2018
- Haiku monthly activity report - 02/2018
- Haiku monthly activity report - 01/2018
- GCI 2017 Wrap Up Report
- Haiku monthly activity report - 12/2017
- New package repositories are now enabled by default
- Haiku monthly activity report - 11/2017
- Scripting the GUI with 'hey'
- Haiku monthly activity report - 10/2017