blob: 285b4a8f881bab8967d2adc97ea42a93812ba160 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<maintainer type="person">
<email>tupone@gentoo.org</email>
<name>Alfredo Tupone</name>
</maintainer>
<maintainer type="project">
<email>python@gentoo.org</email>
<name>Python</name>
</maintainer>
<longdescription lang="en">Buildout is a system for managing development buildouts. While often identified as a Zope project,
and indeed licensed under the ZPL by Zope creator Jim Fulton, buildout is useful for configurations
beyond Zope, and even, in rare cases, a few that have nothing to do with Python.
The Buildout project provides support for creating applications, especially Python applications. It
provides tools for assembling applications from multiple parts, Python or otherwise. An application
may actually contain multiple programs, processes, and configuration settings.
The word .buildout. refers to a description of a set of parts and the software to create and assemble
them. It is often used informally to refer to an installed system based on a buildout definition. For
example, if we are creating an application named .Foo., then .the Foo buildout. is the collection of
configuration and application-specific software that allows an instance of the application to be
created. We may refer to such an instance of the application informally as .a Foo buildout..</longdescription>
<upstream>
<remote-id type="pypi">zc.buildout</remote-id>
</upstream>
</pkgmetadata>
|
GitWeb
