[tor-bugs] #9668 [Flashproxy]: restructure flashproxy source tree

[Tor Bug Tracker & Wiki]

#9668: restructure flashproxy source tree
----------------------------+-----------------
     Reporter:  infinity0   |      Owner:  dcf
         Type:  defect      |     Status:  new
     Priority:  normal      |  Milestone:
    Component:  Flashproxy  |    Version:
   Resolution:              |   Keywords:
Actual Points:              |  Parent ID:
       Points:              |
----------------------------+-----------------

Comment (by infinity0):

 Continuing from [comment:8:ticket:6810]:

 Let me also explain the packaging model. Currently, the top-level Makefile
 has two *binary* distribution targets, a python-source and a py2exe
 zipball. (We call the python-source a "binary" package even though it's
 source-code python, because the intention is to run it directly, there is
 no "install" process, and you don't provide any Makefiles or tests.)

 OTOH for Debian (and good FOSS practise) I am building source packages,
 which include tests and build scripts. Everything is in one source repo at
 the moment, but I am doing source packaging on subfolders to make it
 easier to split the repo later, which you were vaguely talking about
 doing. The top-level Makefile will tie everything together for an all-in-
 one package, but there are two inconsistencies that need sorting:

 1. the top-level Makefile also acts as the sub-Makefile for the client
 programs (mentioned in [comment:3])
 2. `make dist` by convention builds a source package, but the current
 target builds a binary package. I can keep the binary target but will need
 to rename it.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9668#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online