Aren
/
haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs/develop: Document how to build source hpkgs 

Change-Id: I86a6cef5773c543e1b46d85091b9e73a7e3c016c
Reviewed-on: https://review.haiku-os.org/c/haiku/+/5342
Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
Reviewed-by: Adrien Destugues <pulkomandy@gmail.com>
This commit is contained in:
Alexander von Gluck IV 2022-05-24 21:17:30 -05:00 committed by Alex von Gluck IV
parent 143253c873
commit 6ec74693c7
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/develop/packages/Bootstrapping.rst
View File

@ -120,6 +120,27 @@ the target build profile used by the bootstrap process. This defaults to
(i.e. ``jam -sHAIKU_BOOTSTRAP_SOURCES_PROFILE=@release-raw -q @bootstrap-raw``
will include source packages for all packages needed by release image).
Format of hpkg Source Repository
========================
For Haikuporter to use source or "rigged" packages instead of requesting
packages from a remote url (essential during bootstrap when patch, git,
curl, etc are unavailable), haikuporter works on an empty haikuports repository
with the following layout:
- haikuports/input-source-packages
Contains all input source (or source_rigged) hpkgs
- haikuports/FormatVersions
Contains ``RecipeFormatVersion=1`` so haikuporter can identify the haikuports
repository
After ``haikuporter`` is given this directory structure, it will parse the
source or "rigged" packages, and allow you to build them internally replacing
the SOURCE_URI with ``pkg:input-source-packages/``
This process is generally automated during the generation of the bootstrap
image, but manual setup may be needed if the bootstrap image is non-functional
on your target platform.
Haiku Architecture Ports
========================
When preparing a new Haiku architecture port for the bootstrap build the