premake / premake/premake-core
Forced use of contrib makes porting harder
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
I tried to update our haikuports recipe from 4.4 and I'm stuck with cURL failing to build, because it misses a config header for Haiku. Adding a defined(__HAIKU__) to use the linux one of course fails as well…
I understand the concerns for using contribs, but it makes porting harder when you already have the dependencies ported because you have to do all the work again (and yes, our cURL port is already upstream AFAIK). Also, maintaining your own versions of cURL and others means security fixes are not applied even when updating the respective packages… so it's bad security-wise as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked haikuports dev-util/premake recipe and investigate how Premake handles its cURL and other contrib dependencies. Reproduce the cURL configuration-header failure on Haiku and determine the project entry point for choosing bundled versus existing dependencies. Done means the port can use its already-ported dependencies without losing a supported build path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100