Skip to content
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

Licenses #883

Open
rfht opened this issue Sep 9, 2018 · 7 comments
Open

Licenses #883

rfht opened this issue Sep 9, 2018 · 7 comments

Comments

@rfht
Copy link
Contributor

rfht commented Sep 9, 2018

Is your feature request related to a problem? Please describe.
Hi,

As brought up in Issue #630 a while ago, I have a working port for OpenBSD. To share this with other users via the ports system, I'd like to clarify licensing.

The one that I stumbled over is the license in the PortTalk code.

Is PortTalk so important that the restrictive license is justified?

I have looked through the head of all 4,000-something files and didn't see anything else that looked like a restrictive license, but with so many files, I'd just like to know if there may be other code that's known to be similarly copyrighted/licensed.

Describe the solution you'd like
Clarify use of restrictively licensed code or (ideally) find a way to replace or make it optional to use.

Describe alternatives you've considered
Alternatively, a port e.g. on OpenBSD might require manual building and could not be distributed in binary form if this conflicts with some of the licenses used.

Additional context
Sorry for the delay between my original contact in Issue #630 .
If I can be of any help in sorting out the license situation, I'd be glad to help! Thanks for this otherwise awesome project!

@joncampbell123
Copy link
Owner

joncampbell123 commented Sep 9, 2018

I don't consider the PortTalk code important, nor do I think it would even work on OpenBSD.

I did a quick lookover of the source tree sometime back to try and document all licenses and sources of the various parts of the code, which is listed in the README file under "Origins and crediting of source code".

@rfht
Copy link
Contributor Author

rfht commented Sep 15, 2018

Thanks for merging. I've reached out to Neko Project II upstream to find out about the pertaining license. Also looking into FreeDOS again. Would suggest keeping this issue open for a bit since I'm still actively trying to add more info.

@yksoft1
Copy link
Contributor

yksoft1 commented Nov 7, 2018

By the way, DOS4GW.EXE, DOSIDLE.COM and such built-in binary blobs would have licensing problems.

@joncampbell123
Copy link
Owner

Good point.

DOSIDLE.COM could be rewritten from scratch if I can figure out what it does.

DOS4GW.EXE could be eliminated because most games that need it provide their own.

@yksoft1
Copy link
Contributor

yksoft1 commented Nov 7, 2018

Good point.

DOSIDLE.COM could be rewritten from scratch if I can figure out what it does.

DOS4GW.EXE could be eliminated because most games that need it provide their own.

Are such blobs there since DOSBox Daum?

@joncampbell123
Copy link
Owner

That was inherited from Daum's branch, yes.

@CoelacanthusHex
Copy link

Hi, I have a similar issue:
I maintain the package of this project in archlinuxcn. Recently, Arch Linux enforced using the SPDX identifier via RFC161. It differs from GPL-2.0-only and GPL-2.0-or-later. So I need to know which one was used in this project. And need to know all other licenses used by this project.
Thank You!

Footnotes

  1. https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0016-spdx-license-identifiers.rst

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants