Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Provide some platform-specific modules for VMS. #866

Closed
wants to merge 1 commit into from

4 participants

@mvorl

Provide platform-specific versions of entropy.c and exec.c for VMS.

@rurban
Collaborator

See the branch vms-platform-specific. We are having licensing concerns with the 2 stolen files,
one Artistic 2.0 from p5, which should be fine, and one BSD-style, which is causing troubles.
Parrot has a history of rejecting BSD-licensed contributions

@rurban
Collaborator

Split by cotto into the safe vms-exec branch, and into the unsafe vms-entropy branch.

@leto
Owner

+1. I am in the process of applying the Parrot Foundation to the Software Freedom Conservancy and we need to precisely document all the licenses of external code we use. And by "stolen", you mean "lovingly borrowed", right? What were the historical reasons for rejecting BSD-licensed contributions?

@cotto

I believe that "lovingly borrowed" is the correct technical term for what happened here. It appears that the entropy code was implemented primarily by one person (Steven M. Schweda) so it's possible that he'd be willing to let us use it under the Artistic License 2.0, which would be the ideal outcome. @rurban said he'd look into this. If Steven isn't willing to relicense his entropy gathering code, we get to do some navel-gazing and figure out what exactly the incompatibility is that's prevented bsd-licensed code from being incorporated into Parrot in the past and whether we believe that the problem still applies. Since we don't have a real lawyer on retainer for PaFo, I'd prefer to obviate such discussion if possible and get on with hacking.

@mvorl

"lovingly borrowed" is an extraordinarily nice term, and so much better than "stolen" ;-)

Thank you all for your effort WRT entropy.c. I promise I will pay better attention to licensing details in the future.

@cotto

After looking at the vms code, I can't blame you at all for not wanting to reimplement it. Hopefully the code in the entropy branch ends up being usable.

@leto
Owner

What is the status of this? If this PR was split into two different branches, we should create issues' related to each of those branches and close this PR.

@leto
Owner

Any updates on this PR?

@rurban
Collaborator

Yes, tracked in 2 branches:

  • vms-entropy - ready to be merged. Licensed by the author to GPL 3
  • vms-exec

I guess this was the old branch:

  • vms-platform-specific - to delete?

So I rebased and merged those and created smoke-me/vms-gh866 with a few more codingstd fixes.
Needs to be tested by @mvorl for 6.10.0.

@rurban rurban added this to the 7.0.0 milestone
@rurban
Collaborator

Can someone with vms please smoke this?

@rurban
Collaborator

merged into 6.11.0

@rurban rurban closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Nov 4, 2012
  1. @mvorl
Something went wrong with that request. Please try again.