[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2255: Experiment with virtualenv based packaging in the petmail style.

[Tahoe-LAFS]

#2255: Experiment with virtualenv based packaging in the petmail style.
--------------------------+-----------------------
     Reporter:  nejucomo  |      Owner:  daira
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  undecided
    Component:  unknown   |    Version:  1.10.0
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------

Comment (by nejucomo):

 Some notes on how nejucomo generated `./requirements.txt`:

 1. Edited `./setup.py` to rename `support` to `legacysupport`.
 1. renamed `support` to `legacysupport` in `.gitignore`.
 1. recursively copied `./support` from petmail
 1. spliced in the `SafeDevelop` and `run_command` from petmail, but
 renamed the latter to avoid a collision from default tahoe `setup.py`.
 1. Ran `python ./setup.py safe_develop` mainly to initialize `./venv` (but
 perhaps it would be simpler to run `python ./support/virtualenv.py
 ./venv`)
 1. Ran `./venv/bin/pip install .` to use the existing `./setup.*` to
 install dependencies into the new `./venv`.
 1. Generated `requirements.txt` using the existing `./venv` by running
 `./venv/bin/python ./venv/bin/peep.py freeze > ./requirements.txt`
 1. manually removed `wsgiref` and `allmydata-tahoe` from
 `requirements.txt`
 1. deactivated `./venv` then ran `python ./setyp.py safe_develop` to
 trigger peep's display of package hashes.
 1. overwrote `requirements.txt` with the output of peep.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2255#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage