Re: Release plans

[Alan Mackenzie <acm@muc.de>]

Hi, again!

On Thu, Aug 14, 2008 at 01:07:35PM +0200, Johannes Weiner wrote:
> Hi Alan,

> Alan Mackenzie <acm@muc.de> writes:

> > I think the lack of provision of binary libraries is more of a legal
> > thing than a political one.  It would allow people to extend Emacs
> > with non-free code, and it would be problematic to prevent them
> > distributing their enslaved versions of Emacs.

> > I agree with Richard that this would be undesirable in the extreme.
> > Linux has taken the opposite attitude: that extending Linux with
> > non-free modules is OK.  This has not been free of problems.

> I am very sensitive when it comes to such decisions.  Because when you
> try to prevent idiots from being idiots, you will also restrict people
> that could do great work with the potential features.

Just to clarify my previous post, I do see that there are strong points
on both sides of this argument.  My personal view is that the coming into
effective existence of "enslaved" versions of Emacs through the loading
of binary libraries would outweigh the benefits.

> The primary thing about Linux modules is, well, that you can load
> modules.  This gives you power to do really clever stuff.

> Whether one loads proprietary modules into the kernel is a personal
> decision and I don't like deciding for other people.

The loadability of modules into the kernel has effects on the whole free
software community.  Somebody MUST decide this issue for other people,
possibly by default.  In these two cases, the decisions were taken by
Linus Torvalds and Richard Stallman.  It is entirely possible that both
were right.  Now I agree with you about it being a political thing.  ;-)

> I argue with people loading these modules and tell them why I consider
> it stupid but the decision should be their own.

The facility you want would allow people, in effect, to make proprietary
extensions to Emacs.  We could end up with a firm like Linspire saying
"our version of Emacs is superior because it can access files over the
<proprietary X> protocol, so why don't you buy a license for our superior
version of Linux instead of your lame Ubuntu or RedHat?".

I think that this possibility outweighs the benefit from being able to
load in something like the OTR libraries.  At the same time, I respect
your view to the contrary.

> > If there were a way of licensing Emacs so that only free libraries
> > could be attached to it, this would be done.

> Linux prevents certain APIs from being used by non-free modules.  And
> modules have to explicitly identify themselves as GPL-licensed to be
> able to use GPL-only symbols.

I didn't know that.  Thanks!

> IANAL but perhaps a mechanism for Emacs that requires modules to
> announce themselves as GPL'd software would be enough?

More specifically, as GPL3 software.

> > What sort of libraries do you want to use from Emacs anyway?

> I would be interested in having OTR support for jabber.el.  So my
> choice is between implementing the OTR protocol in elisp or linking the
> emacs binary against libotr.

> I consider both solutions bad by design.  The optimal solution would be
> for jabber.el to issue (require 'libotr) and have Emacs doing the right
> thing.

There are other choices.  You could, for example, write a module-loading
facility yourself, and thus distribute your own Emacs fork.  You'ld not
make yourself popular though, any more than the Lucid Emacs crowd did a
long time ago.

Or, you could simply adapt the OTR sources and build them into Emacs.
Well, you could if either the OTR author was prepared to release his
sources under GPL3, or RMS was prepared to accept GPL2 stuff into Emacs.
Hell will freeze over before the second of these happens.  ;-)

> 	Hannes

By the way, do you really live in an acid bath?  ;-)

-- 
Alan Mackenzie (Nuremberg, Germany).