README.md: Remove section for developers (for now)

The developer information about how you can specify the source for
scripts and binaries has been having some problems, including for
upgrades.  The decision not to support upgrades from wheezy makes it
easy to stop supporting wheezy's upgrade mechanism and begin the
migration toward doing it right.  Doing it right places much greater
emphasis on upgrade security and integrity.

The developer side of this was that the scripts ran themselves straight
off a web server.  That's just a problem in general, and it too will be
fixed shortly.

The downloading of binary components is the last thing...  The right way
to do this is follow the lead of @dschmenk and package this stuff
properly which gains us much of that upgrade integrity/security I spoke
of.  That'll be a multi-step migration of its own.

This will be documented as it is implemented, but here's a heads up.

README.md

@@ -13,84 +13,7 @@ relatively modern piece of it.  As such they should be preserved as they are.
 
 ## Developer note
 
-To use the scripts on your own server, including your local machine:
-
-~~~ bash
-export A2SERVER_SCRIPT_URL=http://yoururl.com/
-~~~
-
-To prevent needing to recompile various packages from source code during
-installation, a number of precompiled binary files are downloaded for Raspbian,
-Debian-x86, and Debian-amd64. If you wish to host these on your own server:
-
-~~~ bash
-export A2SERVER_BINARY_URL=http://yoururl.com/files/
-~~~
-
-You do not need to use a subdirectory called "files", or the same server, but
-that's the normal arrangement. The precompiled packages are available here:
-`http://ivanx.com/a2server/files/dist/a2serverbinaries.tar.gz`
-
-Several Apple II third-party binaries are downloaded during installation, as
-well as third-party source code if precompiled binaries are unavailable or
-you don't wish to use them. If you want these external dependencies locally
-during development, they need to go into a folder called "external" in
-the binaries URL, and that needs to contain folders called "appleii" and
-"source". To download all of these external packages, download and run the
-shell script at
-`http://ivanx.com/a2server/files/dist/getexternal.sh`.
-
-Once you have those:
-
-~~~ bash
-export A2SERVER_NO_EXTERNAL=1
-~~~
-
-You may want to put the above exports into `~/.bashrc` or `~/.bash_profile`.
-
-If you want to host scripts locally installed on your own machine or another
-computer on your LAN, type the following, and export "http://localhost:8000/"
-or "http://lan.ip.address:8000/" for the above URL's.
-
-~~~
-python -m SimpleHTTPServer
-~~~
-
-Once you're set, you can then run the following snippet to install A2SERVER:
-
-~~~
-wget -O setup ${A2SERVER_SCRIPT_URL}setup/index.txt; source setup
-~~~
-
-
-Offline install:
-
-Using locally hosted binaries and external dependencies, it's possible to
-install completely offline if dependent packages have been installed.
-
-If precompiled binaries are available, on Wheezy:
-
-~~~
-sudo apt-get -y install unzip libgnustep-base1.22 libdb5.1 libgcrypt11 libssl1.0.0 attr fuse libglib2.0-0 libattr1 libfuse2
-~~~
-
-If precompiled binaries are available, on Jessie:
-
-~~~
-sudo apt-get -y install unzip unar libdb5.3 libgcrypt20 libssl1.0.0 attr fuse libglib2.0-0 libattr1 libfuse2
-~~~
-
-If precompiled binaries are not available, on Wheezy:
-
-~~~
-sudo apt-get -y install unzip build-essential zlib1g-dev libgnustep-base-dev libz-dev libbz2-dev libssl-dev libicu-dev libdb5.1-dev libgcrypt11-dev libglib2.0-dev libattr1-dev libfuse-dev
-~~~
-
-If precompiled binaries are not available, on Jessie:
-
-~~~
-sudo apt-get -y install unzip unar build-essential zlib1g-dev unzip libssl-dev libdb5.3-dev libgcrypt11-dev libglib2.0-dev libattr1-dev libfuse-dev
-~~~
-
+This section used to describe how to run these scripts directly.  That's
+changing.  Watch this space.
 
 [Ivan's site]: http://appleii.ivanx.com/a2server/