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

Software license? #6

Closed
jpcima opened this issue Jun 13, 2019 · 5 comments
Closed

Software license? #6

jpcima opened this issue Jun 13, 2019 · 5 comments

Comments

@jpcima
Copy link
Contributor

jpcima commented Jun 13, 2019

Hi, the software license is not indicated in the source.
I found chiptext.c to be a remarkably helpful debugging tool, and I would like to use it in other software, if vgmtools has a license which permits it.

@felipesanches
Copy link

I am not sure, but maybe this is the same problem as discussed at vgmrips/vgmplay-legacy#47

@superctr
Copy link
Contributor

vgmtools do not contain any emulation code from vgmplay, so it should be encumbered by other licenses. Though chip_cmp, chip_sro etc are to some extent based on the emulators as some state must be emulated in order to optimize VGMs. I'll leave it to @ValleyBell for the final verdict, but as far as I'm concerned, you're free to use my code in this repo for any purpose you want.

@ValleyBell
Copy link
Contributor

If we're very strict, then I guess one could say that chip_cmp/chip_srom/chiptext is based off MAME code, as it borrows comments for switch/case blocks and names for constants/member variables from MAME's sound cores.
The actual logic is mostly my own code though.

In any case, feel free to use the code. I don't have any objections.

@jpcima
Copy link
Contributor Author

jpcima commented Jun 19, 2019

Thanks, really appreciate it, but just a thing: can this source be attributed a license, like MIT or such?
I think a license can be indicated by comments at top of individual files, like in MAME.

It's desirable that I can precisely identify a license for my sources, particularly because debian has an extremely rigorous process when it comes to this.

@ValleyBell
Copy link
Contributor

Here we go ...
fixed by 1903158

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

No branches or pull requests

4 participants