On 24 October 2017 at 10:57, Dmitry Gutov wrote: > On 10/24/17 12:52 PM, Reuben Thomas wrote: > > It's really the question of where development happens that I'm interested >> in. >> > > We've been talking about Flycheck, haven't we? It's not the real issue > with it. > ​The argument was made that we couldn't use it by default because we can't get its copyright assigned to the FSF, so we can't include it as part of Emacs.​ I was arguing that it shouldn't be necessary to have an Elisp package in the repository. However, it might still be necessary to have a default dependency be FSF-copyright; a quick look suggests that, apart from system libraries (libc), all the mandatory dependencies of Emacs are indeed FSF-copyright. Therefore, it might still not be possible to use Flycheck by default (as it might not be possible to obtain copyright assignment even if the current maintainers supported it), but there's no reason why it couldn't be supported at build time, like the various optional C libraries, so that it could "out of the box", just like support for various image formats. -- https://rrt.sc3d.org