unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Zhu Zihao <all_but_last@163.com>
To: rms@gnu.org
Cc: Yuan Fu <casouri@gmail.com>, emacs-devel@gnu.org
Subject: Re: How to distribute dynamic modules by themselves?
Date: Tue, 22 Mar 2022 16:44:35 +0800	[thread overview]
Message-ID: <86bkxytltl.fsf@163.com> (raw)
In-Reply-To: <E1nWWjo-0005h3-Sv@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]


Yes, Xapian is definitely licensed under GPLv2 or later.

And many distributions following FSDG distribute Xapian. IMO, it's OK to
write a module to empower Emacs with Xapian.

Richard Stallman <rms@gnu.org> writes:

> [[[ 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 wrote a dynamic module that exposes a simple interface for
>   > Xapian, the indexing and searching engine. It could be very useful
>   > for indexing thousands of files and search in them. I use this
>   > module for my note-searching package.
>
> This could be a useful thing, but before we decide to install it, we
> need to check some crucial nontechnical issues.
>
> * The moral issues.
> Does Xapian include any nonfree software?
> Does it depend on the presence of any nonfree software?
>
> Does Xapian use some web service?
>
> * The legal issues.
> Assuming Xapian does everything with free software,
> is all that software under GPL-compatible licenses?
> If not, we need to look at how the non-GPL-compatible
> software connects with the GPL-covered body of
> Emacs and its add-ons.  Depending on that, it might be ok.
>
> See https://gnu.org/licenses/license-list.html to check
> whether a license is free, and whether it is GPL-compatible.


-- 
Retrieve my PGP public key:

  gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F

Zihao

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

  reply	other threads:[~2022-03-22  8:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 23:51 How to distribute dynamic modules by themselves? Yuan Fu
2022-03-21  1:31 ` Zhu Zihao
2022-03-22  5:07 ` Richard Stallman
2022-03-22  8:44   ` Zhu Zihao [this message]
2022-03-23  3:55     ` Richard Stallman
2022-03-23 19:44       ` Yuan Fu
2022-03-25  3:29         ` Richard Stallman
2022-03-23 11:20 ` Lars Ingebrigtsen
2022-03-23 19:48   ` Yuan Fu
2022-03-25  3:29     ` Richard Stallman
2022-03-25  5:53       ` Yuan Fu
2022-03-27  5:27         ` Richard Stallman
2022-03-27  5:27         ` Richard Stallman
2022-03-23 22:16   ` Stefan Monnier
2022-03-23 22:30     ` Ergus
2022-03-24  3:19   ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bkxytltl.fsf@163.com \
    --to=all_but_last@163.com \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).