Porting the Hiawatha server to Haiku (3)

Continued from page 2 of Porting …

For the urls, source-urls, and post-install-scripts sections, I used these values:

urls {

source-urls {"https://www.hiawatha-webserver.org/files/hiawatha-10.6.tar.gz"}

post-install-scripts {

For the summary, description, copyrights, and vendor sections, I used quoted text with no particular constraints, other than copyrights started with “Copyright (C)” and all my entries were short.

For the packager entry, I did find I needed to toe-the-typo line, and it seemed to have to follow this kind of format:

  • packager “joe schmo <xxxzzz@somesite.com>”

Messing with the email part of this seemed to squash the package build, unless I remember incorrectly exactly what I did.  There was some trial and error in the manifest figure-out-how-it-works period.  In the end, it installed for me, and I guess that’s what I was after.  I imagine that I’ll find some better things to do, the next time I package an application for Haiku.  Meantime, take all of this with heavy dose of salt, and maybe a prayer or two.

Once the .PackageInfo file was tidied up, I put it into the hiawatha directory (the base of the “fake” directory structure for the package builder), and issued:

  • package create -C ~/hiawatha

The result of the package utility output should be a Haiku package, with the extension “HPKG”.    So, now we go on to the other project builds.

To be continued …

FWIW: the author does not make any claims as to the accuracy of statements in this document. Much of it has been taken from memory.

Note: Hiawatha is hosted at https://www.hiawatha-webserver.org, and this site and author has no affiliation with them. Also, Haiku-OS is an operating system at http://www.haiku-os.org, and this site and author has no affiliation with them.