[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9668 [Flashproxy]: restructure flashproxy source tree
#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):
Replying to [comment:10 dcf]:
> Maybe I misunderstand you. Isn't it typical that many binary packages
are built from one source package? For example, when I `apt-get source
openssh-server`, it informs me that it is actually downloading the source
package "openssh".
> {{{
> [..]
> }}}
> I expected that flashproxy packaging would work the same way: binary
packages "flashproxy-client" and "flashproxy-facilitator", say, built from
a single source package "flashproxy". I don't understand the need to have
multiple source packages, each made from a subdirectory.
Sorry, by "source package" I simply meant a build script that handles a
distinct sub-component. (This makes the packaging process simpler and
enforces good separation of concerns.) For example, the setup.py for
-common and Makefile for -facilitator. The infrastructure for these build
scripts typically also includes "for free" the ability to build a source
tarball, but you are correct that we don't need to actually do this and
distribute them. The important thing is a coherent and well-supported
`install` process.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9668#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs