From 665ffa292f94d2a0dd6a7368852c405869aa1cae Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Sat, 12 Apr 2008 03:10:49 +0000
Subject: [PATCH] edit and update

[Imported from Trac: page Packaging, version 15]
---
 Packaging.md | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/Packaging.md b/Packaging.md
index 9def788..e62f047 100644
--- a/Packaging.md
+++ b/Packaging.md
@@ -3,12 +3,11 @@
 We want to package Tahoe for people to download and use and we want to use
 3rd-party libraries. The following are our current desiderata:
 
- * For certain deployment targets, we can produce a Tahoe binary package for
+ * For certain deployment targets (namely, recent Debian and recent or Long-Term Support Ubuntu), we produce a Tahoe binary package for
    that platform, ship that package to a user using that platform, they can
    install that package, and it will work. That is: user doesn't have to
    manually satisfy any dependencies by building other packages.
-   * For Ubuntu "edgy" and "feisty" platforms, as well as Debian "etch" and "lenny", this
-     is accomplished by adding the following clause to
+   * This is accomplished by adding the following clause to
      `/etc/apt/sources.list` and then running
      `apt-get install allmydata-tahoe`:
 
@@ -16,8 +15,6 @@ We want to package Tahoe for people to download and use and we want to use
 deb http://allmydata.org/debian  $DIST  main tahoe
 ```
 
- * this covers all major Debian and Ubuntu platforms released in the last year.
-
 For libraries that Tahoe uses, we have these desiderata:
 
  * We use the source code as it is written by upstream. That is: no patching