branch: elpa/emacsql
commit 59147c4cdfd18dc2736a6502a3283564ab5c1457
Author: Christopher Wellons <well...@nullprogram.com>
Commit: Christopher Wellons <well...@nullprogram.com>
Update README paragraph about automatic downloads (#46)
---
README.md | 15 ++++-----------
1 file changed, 4 insertions(+), 11 deletions(-)
diff --git a/README.md b/README.md
index 49bc58eb7d..7b6e1fa400 100644
--- a/README.md
+++ b/README.md
@@ -14,17 +14,10 @@ closures. EmacSQL has no concept of "TEXT" values; it's all
just lisp
objects. The lisp object `nil` corresponds 1:1 with `NULL` in the
database.
-On MELPA, each backend is provided as a separate package, suffixed
-with the database name. In the case of `emacsql-sqlite`, on first use
-EmacSQL will attempt to compile a custom native binary for
-communicating with a SQLite database. If this fails (a C compiler is
-not available), it will attempt to download, with permission, a
-pre-built binary when the first database connection is attempted. The
-official sqlite3 command shell is incapable of correct interaction
-when linked with GNU Readline, or when run in Windows, so a custom
-build tool is required. If your own package depends on EmacSQL as a
-database, this means it doesn't have to rely on the user having any
-particular software installed.
+On MELPA, each backend is provided as a separate package, suffixed with
+the database name. In the case of `emacsql-sqlite`, on first use EmacSQL
+will attempt to find a C compiler and use it to compile a custom native
+binary for communicating with a SQLite database.
Requires Emacs 25 or later.
