unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: How to distribute dynamic modules by themselves?
Date: Tue, 22 Mar 2022 23:55:58 -0400	[thread overview]
Message-ID: <E1nWs6I-0001xM-Co@fencepost.gnu.org> (raw)
In-Reply-To: <86bkxytltl.fsf@163.com> (message from Zhu Zihao on Tue, 22 Mar 2022 16:44:35 +0800)

[[[ 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. ]]]

  > Yes, Xapian is definitely licensed under GPLv2 or later.

That eliminates most of the possible problems.  Only one
question remains?

Does Xapian use a web service, or does it do its job locally?

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2022-03-23  3:55 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
2022-03-23  3:55     ` Richard Stallman [this message]
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=E1nWs6I-0001xM-Co@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=all_but_last@163.com \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@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).