rewrite first section of README.rst & Debian package description

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>

2 files changed, 30 insertions, 19 deletions

diff --git a/debian/changelog b/debian/changelog
index 0c8a621..10bea3a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+consfigurator (0.9.2-1) UNRELEASED; urgency=medium
+
+  * Rewrite long description.
+
+ -- Sean Whitton <spwhitton@spwhitton.name>  Sun, 22 Aug 2021 11:39:43 -0700
+
 consfigurator (0.9.1-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index 60cb533..e687ffa 100644
--- a/debian/control
+++ b/debian/control
@@ -51,28 +51,33 @@ Provides:
 Description: Lisp declarative configuration management system
  Consfigurator is a system for declarative configuration management using
  Common Lisp.  You can use it to configure hosts as root, deploy services as
- unprivileged users, build and deploy containers, and produce disc images.
+ unprivileged users, build and deploy containers, install operating systems,
+ produce disc images, and more.  Some key advantages:
  .
- Consfigurator's design gives you a great deal of flexibility about how to
- control the hosts you want to configure.  If there is a command you can run
- which will obtain input and output streams attached to an interactive POSIX
- sh running on the target host/container, then with a little glue code, you
- can use much of Consfigurator's functionality to configure that
- host/container.  But if it is possible to get an implementation of Common
- Lisp started up on the host, then Configurator can transparently execute your
- deployment code over on the remote side, rather than exchanging information
- via POSIX sh.  This lets you use the full power of Common Lisp to deploy your
- configuration.
+  * Apply configuration by transparently starting up another Lisp image on the
+    machine to be configured, so that you can use the full power of Common Lisp
+    to inspect and control the host.
  .
- Configurator has convenient abstractions for combining these different ways
- to execute your configuration on hosts with different ways of connecting to
- them.  Connections can be arbitrarily nested.
+  * Also define properties of hosts in a more restricted language, ``:POSIX``
+    properties, to configure machines, containers and user accounts where you
+    can't install Lisp.  These properties can be applied using just an SSH or
+    serial connection, but they can also be applied by remote Lisp images,
+    enabling code reuse.
+ .
+  * Flexibly chain and nest methods of connecting to hosts.  For example, you
+    could have Consfigurator SSH to a host, sudo to root, start up Lisp, use
+    the setns(2) system call to enter a Linux container, and then deploy a
+    service.  Secrets, and other prerequisite data, are properly passed along.
+ .
+  * Combine declarative semantics for defining hosts and services with a
+    multiparadigmatic general-purpose programming language that won't get in
+    your way.
  .
  Declarative configuration management systems like Consfigurator and Propellor
  share a number of goals with projects like the GNU Guix System and NixOS.
  However, tools like Consfigurator and Propellor try to layer the power of
- declarative and reproducible configuration on top of traditional,
- battle-tested unix system administration infrastructure like apt, dpkg, yum,
- and distro package archives, rather than seeking to replace any of those.
- Let's get as much as we can out of all that existing distro policy-compliant
- work!
+ declarative and reproducible configuration semantics on top of traditional,
+ battle-tested UNIX system administration infrastructure like distro package
+ managers, package archives and daemon configuration mechanisms, rather than
+ seeking to replace any of those.  Let's get as much as we can out of all that
+ existing distro policy-compliant work!