From bd059ebb0c19c346f463d0d71d10c409c9f469a4 Mon Sep 17 00:00:00 2001
From: warner <>
Date: Tue, 23 Nov 2010 07:27:11 +0000
Subject: [PATCH] trim the quickstart.html goals

[Imported from Trac: page Packaging, version 23]
---
 Packaging.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Packaging.md b/Packaging.md
index ede942c..06d9217 100644
--- a/Packaging.md
+++ b/Packaging.md
@@ -9,7 +9,7 @@ The setup method that we offer to people when we don't know what platform they a
  * The quickstart.html should *not* instruct the user to install any dependency if the build system could instead satisfy that dependency automatically (currently, as of 2010-09-18, the only dependencies that can't be satisfied automatically are python, and pywin32 which is needed only on Windows).
  * The quickstart.html is intended to be as simple as possible. Options (you can do it this way or that way as you prefer) or branches (if you are in this situation do this, else do that) are strongly discouraged from being written into quickstart.html. If at all possible, please move those to [AdvancedInstall](AdvancedInstall).
 
-The goal is that if the user starts with a system that has nothing installed on it (no Python, no compiler, etc.), but it has a network connection, they can follow the instructions in quickstart.html, which instruct them to install Python, and pywin32 if they are on Windows, and download the Tahoe-LAFS source code, and run `python setup.py build`, and then they'll have a `bin/tahoe` that works.
+The goal is to start with a bare OS and a network connection (no Python, no compiler) and get to a working `./bin/tahoe` by downloading a few things and running `setup.py build` (which downloads the rest).
 
 ### binary .egg's of dependency native-code packages