From e9e672d983902f68964356173ac5a1fc908a10f6 Mon Sep 17 00:00:00 2001
From: Josh Datko <jbd@cryptotronix.com>
Date: Sat, 20 Aug 2016 22:06:43 -0600
Subject: [PATCH] Doc changes.

---
 NEWS      |  4 ++++
 README.md | 15 +++++++++++----
 2 files changed, 15 insertions(+), 4 deletions(-)

diff --git a/NEWS b/NEWS
index 8eeb843..3f19549 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,7 @@
+Noteworthy changes in version 1.1.1 (Saturday, 20 August 2016)
+--------------------------------------------------------------
+  * Small build fixes re: guile
+
 Noteworthy changes in version 1.1 (Wednesday, 15 June 2016)
 ----------------------------------------------------
   * Adds AES GCM 128.
diff --git a/README.md b/README.md
index a75f749..a21fe7f 100644
--- a/README.md
+++ b/README.md
@@ -21,19 +21,26 @@ These algorithms are:
 
 # Getting yacl
 
-On Ubuntu:
-Check the [Cryptotronix PPA](https://launchpad.net/~cryptotronix/+archive/ubuntu/ppa).
-
 Otherwise, probably best to pull the latest
 [release](https://github.com/cryptotronix/yacl/releases). Otherwise,
 you'll need autotools to build this from source. It follows the normal
 autotools dance.
 
+# Configuring yacl
+
+On a full-up-round linux system, I configure yacl like this:
+`./configure --with-libglib -with-guile --with-libsodium
+--enable-tests`
+
+On a debian-based system, you'd probably have to do:
+
+`apt install build-essential libsodium-dev guile-2.0-dev libglib2.0-dev`
+
 
 # Installing yacl
 
 yacl can be installed in the normal fashion, with `sudo make
-install`. I probably should make a .deb out of this to make it
+install && sudo ldconfig`. I probably should make a .deb out of this to make it
 easier...
 
 # Using yacl