emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Flymake support for C/C++


From: Reuben Thomas
Subject: Re: [PATCH] Flymake support for C/C++
Date: Wed, 18 Oct 2017 11:18:30 +0100

On 18 October 2017 at 05:03, Richard Stallman <address@hidden> wrote:
[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > ​I'm having a hard time here making myself clear, it seems! I am not
  > suggesting copyright assignment, I am not suggesting pulling the sources
  > into the Emacs repo, I am merely suggesting shipping Flycheck with Emacs.

If we did that sort of thing, we would make trouble for ourselves, so
our policy is not to do so.

We use various non-FSF-copyright C libraries. We don't ship their sources, it's true
​.


We're already working on making it possible to remove from git Emacs Lisp packages that are shipped in source releases:​


http://lists.gnu.org/archive/html/emacs-orgmode/2016-12/msg00401.html

[I wrote:]

> 2. Is there any possibility to make org-mode a build-time dependency of
> Emacs, like the C libraries that it requires, or is that a silly idea? That
> could permit it to be shipped as built-in, without having its source
> duplicated in Emacs's repository.

[Philip Lord replied:]

This kind of idea is, indeed, being actively considered on
emacs-devel. In fact, I managed to get a simple version of this working
using package.el during the build process. The idea would be that
packages in ELPA format could be made available to Emacs during the

We have been doing this with C code for years; I look forward to our working out how to do it with Elisp too, so that we can reap the same benefits: a wider range of functionality combined with more loosely-coupled code and development processes.

--

reply via email to

[Prev in Thread] Current Thread [Next in Thread]