Info2: << Package: buildbot-py%type_pkg[python] # no simplejson-py24: # Distribution: (%type_pkg[python] = 24) 10.4, (%type_pkg[python] = 24) 10.5 Type: python (2.5 2.6) Version: 0.8.0 Revision: 2 Depends: python%type_pkg[python], twisted2-py%type_pkg[python], twisted2-mail-py%type_pkg[python], twisted2-web-py%type_pkg[python], twisted2-words-py%type_pkg[python], jinja2-py%type_pkg[python], simplejson-py%type_pkg[python], pysqlite2-py%type_pkg[python], setuptools-py%type_pkg[python] # For patchfile: BuildDepends: fink (>= 0.24.12) Source: http://pypi.python.org/packages/source/b/buildbot/buildbot-%v.tar.gz ### The SF mirror will probably be deprecated in the future: #Source: mirror:sourceforge:buildbot/buildbot-%v.tar.gz Source-MD5: 0ab95146d6acb25f0d39c814852d0f6c PatchFile: buildbot-py.patch PatchFile-MD5: cc4d26405616de0994eba2cebd174d45 DocFiles: CREDITS NEWS README CompileScript: << python%type_raw[python] setup.py build << InstallScript: << #!/bin/sh -ev python%type_raw[python] setup.py install --root=%d mkdir -p %i/share/doc/%n cp -pr docs %i/share/doc/%n cp -pr contrib %i/share/doc/%n mv %i/bin/buildbot %i/bin/buildbot%type_raw[python] [ -r PKG-INFO ] && cp -p PKG-INFO %i/share/doc/%n || true << InfoTest: << TestScript: PYTHONPATH=. trial%type_raw[python] buildbot.test || exit 2 TestSuiteSize: medium << PostInstScript: << update-alternatives --install %p/bin/buildbot buildbot %p/bin/buildbot%type_raw[python] %type_pkg[python] << PreRmScript: << if [ $1 != "upgrade" ]; then update-alternatives --remove buildbot %p/bin/buildbot%type_raw[python] fi << Description: Automatic software build/test system DescDetail: << The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve. The overall goal is to reduce tree breakage and provide a platform to run tests or code-quality checks that are too annoying or pedantic for any human to waste their time with. Developers get immediate (and potentially public) feedback about their changes, encouraging them to be more careful about testing before checkin. It is suggested that you start buildbot from launchd: http://buildbot.net/trac/wiki/UsingLaunchd << DescPackaging:<< This package should eventually provide a system user to isolate the builds. << License: GPL Homepage: http://buildbot.net/ Maintainer: Charles Lepple # Info2: <<