-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New license request: Sun-RPC [SPDX-Online-Tools] #906
Comments
Hmm. The online tool didn't put in the license text, and the second source… Here it is:
|
the license text is in the online tool. I know, it's a bit confusing in that way, but it is accessible. thanks! |
Thanks @rohieb. Given SPDX's license inclusion principles, the additional constraint you noted in your comments gives me pause. A restriction on redistribution leads me to think that this likely doesn't meet the bar for inclusion on the SPDX license list. That said, anyone can still reference this license (and any other license not on the license list) in an SPDX document using a user-defined |
FWIW, this has been tracked in ScanCode as the sun-rpc license for as long as ScanCode has existed https://github.com/nexB/scancode-toolkit/blob/develop/src/licensedcode/data/licenses/sun-rpc.LICENSE |
On Sat, Jul 27, 2019 at 11:56:58AM -0700, Steve Winslow wrote:
Thanks @rohieb. Given SPDX's [license inclusion principles](https://github.com/spdx/license-list-XML/blob/master/DOCS/license-inclusion-principles.md), the additional constraint you noted in your comments gives me pause. A restriction on redistribution leads me to think that this likely doesn't meet the bar for inclusion on the SPDX license list.
Right, that seems resonable to me, so I'll close this issue.
- Roland
|
SPDX rejected Sun RPC license due to restriction on redistribution[^1]. Fedora also classified license as not-allowed due to restrictions[^2]. At the same time as removal, we add glibc-based copy in `rpcsvc-proto`, which ships `rpcgen` after it was relicensed. Alternatively, the OpenBSD copy[^3] could be distributed, but versioning is more complicated. If Apple's `rpcgen` is updated to relicensed source, then `rpcgen` may be re-introduced with an updated `license` stanza. [^1]: spdx/license-list-XML#906 [^2]: https://gitlab.com/fedora/legal/fedora-license-data/-/blob/main/data/LicenseRef-sun-rpc.toml [^3]: openbsd/src@cb7760d
1. License Name: Sun RPC License
2. Short identifier: Sun-RPC
3. License Author or steward:
4. Comments: Found in portmap, which was apparently forked from an old version of the Sun RPC code, which has since been relicensed to BSD-3-Clause (see https://github.com/Distrotech/rpcbind/blob/master/src/pmap_svc.c).
The text is similar to the Rdisc license, but includes the additional constraint: "Users may copy or modify Sun RPC without charge, but are not authorized to license or distribute it to anyone else except as part of a product or program developed by the user or with the express written consent of Sun Microsystems, Inc."
5. Standard License Header:
6. URL: https://fossies.org/linux/portmap/portmap.c
7. OSI Status: Not Submitted
The text was updated successfully, but these errors were encountered: