-
Notifications
You must be signed in to change notification settings - Fork 17
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
Submit for inclusion in Emacs? #20
Comments
I suspect the only way for this ffi to be included in emacs would be to enforce gpl compliance like it's done in emacs when loading modules i.e. checking for the presence of a "plugin_is_gpl_compatible" symbol. |
Is it acceptable from an FSF perspective to allow a package option to selectively check for this symbol? That way folks who believe they should only use GPL-compatible software can be assured they'll continue to do so without the side-effect of holding up everyone else. One thing I think is necessary to consider here is whether FF-interfaced libraries are considered 'compiled together' in a way that is potentially incompatible with the GPL/v2/v3. If emacs-ffi were to be released as part of emacs, then using a non-GPL library would be no different (in theory, and in my opinion) than running a non-GPL tool via |
You have to ask on the emacs-devel mailing list. |
Yep. |
I'm completely fine with submitting it for inclusion. I have assignment papers; and I think probably the other contributions are small enough not to need them. John W. asked on irc the other day if I'd do it, so I may send an email to emacs-devel. I think the major issues are the dlopen/symbol-checking thing, and perhaps that the API still has some warts. Oh and there are some bugs, but some of those would be easier to fix in-core. |
Did you move forward with this? |
Have you considering submitting this project for inclusion in Emacs? If this FFI and libffi were part of the standard Emacs distribution, FFI-using libraries would be much, much more convenient to develop and distribute.
The text was updated successfully, but these errors were encountered: