Ports Tree

A ports tree for HaikuPorter structurally follows  Gentoo's package tree. It uses a twofold hierarchy of folders to organize all the ports: the first level of folders represent categories and within each category there's a folder for each port.

Each port folder may contain the following:

• build recipes: at least one build recipe is required for the port to be useful.
• patches: for each version of the port, one generic and a set of architecture-specific patchsets may exist in the patches subfolder
• licenses: each port may specify one or more license files in the licenses subfolder.

Apart from the category folders, each port tree makes us of a repository folder (where the set of to-be-built packages is cached) and a packages folder (where the built packages are collected).

The Standard Ports Tree

The standard ports tree contains the large collection of ports that produce the packages that can be downloaded from the official Haiku package repositories.

You find HaikuPorter's standard ports tree here:  https://bitbucket.org/haikuports/haikuports

The Cross-Build Ports Tree

The cross-build ports tree contains ports that are required for porting Haiku to a new machine architecture or when a binary incompatible change has been made to one of the existing Haiku architecture, and all the packages need to be cross-built from the old to the new version of Haiku.

The ports in this ports tree still follow the Gentoo's categorization, but their name has been suffixed with '_bootstrap' to make it clear that these are cross-compiled packages. There are two exceptions, though: the binutils and the gcc ports have been suffixed with '_cross_<architecture>' in order to clarify that these are the buildtools that implement the cross-build from one architecture to another.

You find HaikuPorter's cross-build ports tree here:  https://bitbucket.org/haikuports/haikuports.cross.