summaryrefslogtreecommitdiff
path: root/net/py-medusa/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2014-05-09Mark packages that are not ready for python-3.3 also not ready for 3.4,wiz1-2/+2
until proven otherwise.
2014-01-25Mark packages as not ready for python-3.x where applicable;wiz1-2/+3
either because they themselves are not ready or because a dependency isn't. This is annotated by PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z or PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar respectively, please use the same style for other packages, and check during updates. Use versioned_dependencies.mk where applicable. Use REPLACE_PYTHON instead of handcoded alternatives, where applicable. Reorder Makefile sections into standard order, where applicable. Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default with the next commit. Whitespace cleanups and other nits corrected, where necessary.
2012-10-23Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-3/+1
2011-06-14distutilify.obache1-3/+3
Bump PKGREVISION.
2008-06-12Add DESTDIR support.joerg1-1/+3
2006-11-04Initial import of py-medusa-0.5.4:wiz1-0/+17
Medusa is a 'server platform' -- it provides a framework for implementing asynchronous socket-based servers (TCP/IP and on Unix, Unix domain, sockets). An asynchronous socket server is a server that can communicate with many other clients simultaneously by multiplexing I/O within a single process/thread. In the context of an HTTP server, this means a single process can serve hundreds or even thousands of clients, depending only on the operating system's configuration and limitations. Medusa includes HTTP, FTP, and 'monitor' (remote python interpreter) servers. Medusa can simultaneously support several instances of either the same or different server types - for example you could start up two HTTP servers, an FTP server, and a monitor server. Then you could connect to the monitor server to control and manipulate medusa while it is running.