-
Notifications
You must be signed in to change notification settings - Fork 31
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
Licence/Copyright issues #144
Comments
Thank you for bringing up these issues. I understand the importance of removing conflicting licensing statements to avoid confusion, even when they are practically irrelevant.
I will promptly fix this in the main branch, and the changes will be reflected in MOPAC's next release. |
Many thanks for the prompt response! In the meantime, I have uploded mopac to Debian with those two files (and thus also the makpol binary) removed, and it was accepted in the archive: https://tracker.debian.org/pkg/mopac I'll reinstate makpol when then next version is released without the two files. |
The Debian Linux distribution did a copyright/license audit before adding mopac to its package repository, and two issues came up:
src/deprecated/Password.F90
has pretty obviously a lot of EULA/proprietary parts in it. As the directory names says, it is deprecated, could it be removed from the codebase? Unfortunately, Linux distributions need to care about source code being distributable under an open source license as well, not just the binaries, so the fact that this file is not compiled by default does not help much.src/makpol/standard.F90
has a weird! 'All Rights Reserved, Copyright (C) Fujitsu Limited 1993.'
at the top of thebangle
subroutine that is not (to my knowledge) in the original MOPAC7 source code, see e.g. https://github.com/lamoureux-lab/MOPAC/blob/master/xyzint.f#L341 Do you have an explanation for that? Can it be removed? I guess that subroutine is needed for at leastmopac-makpol
? "All Rights Reserved" implies this is proprietary code and would also make the codebase not distributable for us.The text was updated successfully, but these errors were encountered: