Changes between Version 8 and Version 9 of Packaging


Ignore:
Timestamp:
2007-08-21T23:59:59Z (17 years ago)
Author:
warner
Comment:

update section on debian packaging

Legend:

Unmodified
Added
Removed
Modified

  • Packaging

    v8 v9  
    11= Packaging =
    22
    3 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:
     3We want to package Tahoe for people to download and use and we want to use
     43rd-party libraries. The following are our current desiderata:
    45
    5  * We can produce a Tahoe binary package for a given deployment target, 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.  The only deployment target that we currently support is Ubuntu Feisty or newer.
     6 * For certain deployment targets, we can produce a Tahoe binary package for
     7   that platform, ship that package to a user using that platform, they can
     8   install that package, and it will work. That is: user doesn't have to
     9   manually satisfy any dependencies by building other packages.
     10   * For Ubuntu "edgy" and "feisty" platforms, as well as Debian "etch", this
     11     is accomplished by adding the following clause to
     12     {{{/etc/apt/sources.list}}} and then running
     13     {{{apt-get install allmydata-tahoe}}}:
     14
     15{{{
     16deb http://allmydata.org/debian  $DIST  main tahoe
     17}}}
     18
     19 * this covers all major debian-derived platforms released in the last year.
    620
    721For libraries that Tahoe uses, we have these desiderata:
    822
    9  * We use the source code as it is written by upstream. That is: no patching required.
     23 * We use the source code as it is written by upstream. That is: no patching
     24   required.
    1025
    11  * Use it as it is packaged by upstream. That is: we prefer to get a copy of the source code of the package as upstream prefers to distribute such source code, rather than by pulling from their revision control tool or so on.
     26 * Use it as it is packaged by upstream. That is: we prefer to get a copy of
     27   the source code of the package as upstream prefers to distribute such
     28   source code, rather than by pulling from their revision control tool or so
     29   on.
    1230
    13  * The user doesn't have to manually resolve any conflicts (this means that we either have to automatically use a 3rd-party library if it is already installed or else we have to automatically force Tahoe to use the copy that it came bundled with).
     31 * The user doesn't have to manually resolve any conflicts (this means that
     32   we either have to automatically use a 3rd-party library if it is already
     33   installed or else we have to automatically force Tahoe to use the copy
     34   that it came bundled with).
    1435
    15  * Make it convenient for someone to use other versions of the packages that we use e.g. system-wide packages or newer or alternate versions, etc..
     36 * Make it convenient for someone to use other versions of the packages that
     37   we use e.g. system-wide packages or newer or alternate versions, etc..
    1638
    17  * Bundle required libraries with the Tahoe distribution so that if someone downloads the distribution, moves to a desert island without a net connection, and then installs, it works.
     39 * Bundle required libraries with the Tahoe distribution so that if someone
     40   downloads the distribution, moves to a desert island without a net
     41   connection, and then installs, it works.
    1842
    1943