move common code into a separate flashproxy-common package
move common/flashproxy to top-level
rename setup.py to be more specific and restricted in purpose
split Makefile into source-level vs binary-level packaging scripts
- Makefile retains the same behaviour as before and builds dist/dist-exe
- Makefile.client acts on the client component only, following GNU standards
- work around wine bug
get rid of dist in Makefile.client, it's not needed and causes problems in the PTBB
- DISTNAME is propagated from Makefile, which in PTBB is set to "flashproxy-client"
- This results in a cyclic dependency since $(DISTNAME) depends on $(SRC_ALL) which includes flashproxy-client, the file
Don't rebuild man pages with "make dist".

This often caused a problem when making bundles, when unpredictable
timestamps after cloning would sometimes cause the man pages to appear
to be out of date. Then the whole build would stop, failing to find the
necessary a2x binary. kpdyer reported this problem in #9940.
Remove ":" command.

Not sure why it was like this.
Add the (default) missing transport arg to put_reg in reg-daemon.
Fix a type error in a log message.

  File "./facilitator", line 333, in do_PUT
    return self.error(u"Unrecognized transport: %s" % transport)
TypeError: not all arguments converted during string formatting
Update documentation of get_reg.
Undo facilitator logging in facilitator-test.
Remove debugging lines in tests.
Fix the PROXY_TRANSPORT log message.

It's not that PROXY_TRANSPORT is missing FROM, it's that GET is missing
PROXY_TRANSPORT.
Use the imp module to import from the facilitator program.
It looks like RELAYS is unused.
Use the name RELAYS in place of SERVERS.

To match the terminology used elsewhere.
Remove obsolete comment.
Don't pun different data types behind the same variable name.

You parse a string such as "obfs3|websocket" to get a Transport.
Set test relay addrs and transports from variables.