Skip to content

Permissive License #5

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

Open
NOP0 opened this issue Nov 12, 2019 · 3 comments
Open

Permissive License #5

NOP0 opened this issue Nov 12, 2019 · 3 comments

Comments

@NOP0
Copy link

NOP0 commented Nov 12, 2019

Would you consider using a permissive license like MIT/Apache?

Thanks

@progval
Copy link
Owner

progval commented Nov 12, 2019

Hello,

I will consider it, but I have other priorities for the moment, including rewriting the code-generator.
What would your use case be?

@NOP0
Copy link
Author

NOP0 commented Nov 12, 2019

Hi, I'm also investigating using rust-xml-schema for parsing 61131-3 XML files. Now that I come to think of it, is the generated parser also under AGPL? Would it be possible to link with the generated parser without getting copyleft?

I'm not a lawyer. 😄

Please, don't consider this issue a priority (and do close it if you think it's off-topic). 👍

@progval
Copy link
Owner

progval commented Nov 12, 2019

is the generated parser also under AGPL?

The *generated parser's code (which is generated Rust code): I'm not sure, but I think not. It's the same problem as with the output of GCC for example.

However, the generated parser heavily uses macros from and needs to link with a runtime, and that one is AGPL yeah.

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

2 participants