4 ms·

A few developers do, and I know of one company that deploys Haiku commercially (TuneTracker: http://tunetrackersystems.com/ http://tunetrackersystems.com/). I

A few developers do, and I know of one company that deploys Haiku commercially (TuneTracker: http://tunetrackersystems.com/ http://tunetrackersystems.com/). I haven't reached that point myself; I'm still missing WiFi support on my laptop (hence why there's so many commits from me working on that area of the system recently ;) But I'm getting close.

tombert 8y ago
I'm interested in this; how much work is it typically to port a package over? EDIT: I'm asking specifically a command-line package.
- waddlesplash 8y ago
  Depends on the package. CLI tools that already work both Linux and some *BSD usually are pretty easy to port, often requiring only a small set of patches. GUI tools that use Qt shouldn't be too tricky either (the LibreOffice port is based on the Qt backend.) Other than that, it varies greatly by application. HaikuPorts (https://github.com/haikuports/haikuports https://github.com/haikuports/haikuports) is what handles the bulk of the work to get applications up and running. I guess the Ninja recipe (https://github.com/haikuports/haikuports/blob/master/dev-util/ninja/ninja-1.8.2.recipe https://github.com/haikuports/haikuports/blob/master/dev-uti...) and patchset (https://github.com/haikuports/haikuports/blob/master/dev-util/ninja/patches/ninja-1.8.2.patchset https://github.com/haikuports/haikuports/blob/master/dev-uti...) are pretty typical for a CLI app, and the Qupzilla recipe (https://github.com/haikuports/haikuports/blob/master/www-client/qupzilla/qupzilla-1.8.9.recipe https://github.com/haikuports/haikuports/blob/master/www-cli...) and patchset (https://github.com/haikuports/haikuports/blob/master/www-client/qupzilla/patches/qupzilla-1.8.9.patchset https://github.com/haikuports/haikuports/blob/master/www-cli...) are roughly typical for a Qt app. If you have some specific application you're trying to port, joining Freenode#haiku and then asking around may be worth your time. :)

tombert 8y ago

I'm interested in this; how much work is it typically to port a package over? EDIT: I'm asking specifically a command-line package.

waddlesplash 8y ago
Depends on the package. CLI tools that already work both Linux and some *BSD usually are pretty easy to port, often requiring only a small set of patches. GUI tools that use Qt shouldn't be too tricky either (the LibreOffice port is based on the Qt backend.) Other than that, it varies greatly by application. HaikuPorts (https://github.com/haikuports/haikuports https://github.com/haikuports/haikuports) is what handles the bulk of the work to get applications up and running. I guess the Ninja recipe (https://github.com/haikuports/haikuports/blob/master/dev-util/ninja/ninja-1.8.2.recipe https://github.com/haikuports/haikuports/blob/master/dev-uti...) and patchset (https://github.com/haikuports/haikuports/blob/master/dev-util/ninja/patches/ninja-1.8.2.patchset https://github.com/haikuports/haikuports/blob/master/dev-uti...) are pretty typical for a CLI app, and the Qupzilla recipe (https://github.com/haikuports/haikuports/blob/master/www-client/qupzilla/qupzilla-1.8.9.recipe https://github.com/haikuports/haikuports/blob/master/www-cli...) and patchset (https://github.com/haikuports/haikuports/blob/master/www-client/qupzilla/patches/qupzilla-1.8.9.patchset https://github.com/haikuports/haikuports/blob/master/www-cli...) are roughly typical for a Qt app. If you have some specific application you're trying to port, joining Freenode#haiku and then asking around may be worth your time. :)