Contrary to the sysutils/vm-bhyve port which tracks releases,
this port will track the head of the main branch. The main reason
is that upstream has become stale in creating releases. This way
we atleast get some improvements that have not yet been included
in a release. Last release dates from January 2020.
Details
Details
- Reviewers
0mp philip manu - Commits
- R11:109cfc001b4e: sysutils/vm-bhyve-devel: add new port
Diff Detail
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
sysutils/vm-bhyve-devel/Makefile | ||
---|---|---|
0โ1 | This has to be something different. Ideally, use git describe --tags to get the version. See the porters handbook for details. Also, if there are some patches in the PRs that are worth bringing in, use PATCH_SITES and PATCHFILES. See the ports tree for examples. | |
sysutils/vm-bhyve-devel/pkg-message | ||
20 | I'd drop that. It's not relevant as it is a new port. | |
sysutils/vm-bhyve/Makefile | ||
3 | I'm not sure if that's necessary, but my guess is that if we want the conflict information to be included in the vm-bhyve package, we have to bump the revision here. So it seems correct. |
Comment Actions
- Use decent versioning based on git describe --tags
- Drop upgrade note as its a new port