devel/p4 and devel/p4api are BSD licensed, even though the distfile does not
include any license file. The source for these ports is separately
distributed through swarm.workshop.perforce.com, and Perforce support
assures me that the license found in the source also applies to the binary
distfile used by these ports.
Details
Details
- Reviewers
gordon mat - Commits
- rP430481: remove RESTRICTED from devel/p4 and devel/p4api
Diff Detail
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Sadly, no, for two reasons:
- The open source release of p4 lags behind the binary release. Basically, perforce's developers work on the binary release, and the community relations team copies that code into the open source repository on their own schedule. And the lag can be many months.
- Perforce has no stable distfiles. It's like the "download zip" button from Github. Whenever the repository changes, the download changes. This causes havoc with Ports, and it also makes me skeptical of the code's stability. Technically, the binary release doesn't have stable distfiles either, but at least it doesn't change continuously.
I've tried explaining to Perforce why their release practices suck, but they don't seem to understand.
Comment Actions
Last time I checked (and it was like 2 months ago) redistribution was strictly forbidden, this would be a real, real, change on their side.
Comment Actions
Catherine Louis of Perforce's support department assures me that the BSD license present in swarm.workshop.perforce.com also applies to the binaries distributed from ftp.perforce.com. Note however that of the things we package, only p4, p4api, and rubygem-p4ruby are on swarm.workshop.perforce.com. p4d, p4p, etc will remain restricted.
Comment Actions
Sure.
Note that the maintainer timeout thingie in the ports tree is about the PR, not about a code review :-)
So if you want to claim a timeout, it should be put in a PR.