adamfowleruk
Haiku App Package Config and Build utility
I think the biggest hurdle after developing and compiling a Haiku application is doing the package work. It would be great to have the ability to configure and build the package (*.hpkg) from Paladin IDE.
Funnily enough I was just thinking of this yesterday. :) My workflow for Paladin is:-
- Dev a feature (Tests first TDD)
- Run tests to check it works and to find any regressions
- Merge feature branch to develop
- Export latest translation work (but don't wait for it to all be finished...)
- When develop ready, merge to master, tag as version and release
- Update hpkg recipe on haikuports for latest release
- Build hpkg successfully (64 and 32 bit)
- PR for new working recipe
The more of that I can automate the better. Ideally point Paladin to the main project PLD, the tests PLD, and the recipe in haikuports and saying "Have at it".
Is this the kind of thing you were thinking?
it could make sense to run the "package" tool directly and build an hpkg file without the help of haikuports, for distribution outside the haikuports repository.
@pulkomandy Sounds like it will work... How do things wind up listed in HaikeDepot outside of HaikuPorts?
You can create alternative repositories (using the package_repo) tool and let users add these using pkgman or Repositories preferences. Or you can just put the hpkg file online or give them to people on whatever convenient media, and they can install it with a double click.
For the official haikuports repo, going through a recipe is required because haikuporter does some sanity checks and ensure a minimal level of QA.
Useful background material. Some discussion about packaging options: https://discuss.haiku-os.org/t/how-to-distribute-an-application-for-haiku-users/9161/3