You are here: Home / LBN / Up2date / Plone and Zope / BastionLinux 25 / zope-zc.buildout-2.12.2-1.lbn25.noarch

zope-zc.buildout-2.12.2-1.lbn25.noarch

Package Attributes
RPM  zope-zc.buildout-2.12.2-1.lbn25.noarch.rpm Architecture  noarch Size  1113946 Created  2021/11/29 02:43:15 UTC
Package Specification
Summary System for managing development buildouts
Group Application/Internet
License ZPL 2.1
Home Page http://www.python.org/pypi/zc.buildout
Description

Buildout is a project designed to solve 2 problems:

  1. Application-centric assembly and deployment

    Assembly runs the gamut from stitching together libraries to create a running program, to production deployment configuration of applications, and associated systems and tools (e.g. run-control scripts, cron jobs, logs, service registration, etc.).

    Buildout might be confused with build tools like make or ant, but it is a little higher level and might invoke systems like make or ant to get it's work done.

    Buildout might be confused with systems like puppet or chef, but it is more application focused. Systems like puppet or chef might use buildout to get their work done.

    Buildout is also somewhat Python-centric, even though it can be used to assemble and deploy non-python applications. It has some special features for assembling Python programs. It's scripted with Python, unlike, say puppet or chef, which are scripted with Ruby.

  2. Repeatable assembly of programs from Python software distributions

    Buildout puts great effort toward making program assembly a highly repeatable process, whether in a very open-ended development mode, where dependency versions aren't locked down, or in a deployment environment where dependency versions are fully specified. You should be able to check buildout into a VCS and later check it out. Two checkouts built at the same time in the same environment should always give the same result, regardless of their history. Among other things, after a buildout, all dependencies should be at the most recent version consistent with any version specifications expressed in the buildout.

    Buildout supports applications consisting of multiple programs, with different programs in an application free to use different versions of Python distributions. This is in contrast with a Python installation (real or virtual), where, for any given distribution, there can only be one installed.

To learn more about buildout, including how to use it, see http://buildout.org/.

Requires
python-setuptools  
/usr/bin/python2  
rpmlib(FileDigests)  
rpmlib(PartialHardlinkSets)  
rpmlib(CompressedFileNames)  
rpmlib(PayloadFilesHavePrefix)  
zope-zc  
rpmlib(PayloadIsXz)  
Provides
python-zc.buildout
python2-zc.buildout
python2.7dist(zc.buildout)
python2dist(zc.buildout)
zope-zc.buildout
Obsoletes
zope-zc.buildout-egginfo

Document Actions