/ / Suche nach buildout.cfg für alte Version von Plone (vor 3.2) [geschlossen] - plone, buildout, plone-3.x

Suche nach buildout.cfg für alte Version von Plone (vor 3.2) [geschlossen] - plone, buildout, plone-3.x

Gibt es eine wiederholbare Möglichkeit, ältere Sample-Buildouts zu generieren?

Speziell suche ich nach einem Buildout-Formatdas ist für die Releases vor Plone 3.2 verwendet worden, da es das erste Release war, das standardmäßig mit Buildout ausgeliefert wurde. Ich weiß, dass es für Plone 3.x Buildouts gibt, aber googeln für das half mir nicht.

Ich versuche ein Plone 3.0 zu konvertieren.Ich möchte einen wiederholbaren, dokumentierten Installationsprozess erhalten, bevor ich herausfinden kann, was ich mit der Codebase machen soll, und die meisten zugänglichen Beispiele sind für Plone 4.x

Antworten:

3 für die Antwort № 1

Dies ist eine grundlegende Vorlage von paster create -t plone3_buildout (alter ZopeSkel <3.0). Ich habe Plone Version 3.1 unten verwendet, Sie müssen es mit Ihrer Version anpassen (... oder einfach: benutzen Sie ZopeSkel wie ich).

[buildout]
parts =
plone
zope2
productdistros
instance
zopepy

versions = versions


# Add additional egg download sources here. dist.plone.org contains archives
# of Plone packages.
find-links =
http://dist.plone.org
http://dist.plone.org/thirdparty

# Add additional eggs here
# elementtree is required by Plone
eggs =
elementtree

# Reference any eggs you are developing here, one per line
# e.g.: develop = src/my.package
develop =

[versions]
# Version pins for new style products go here
plone.recipe.zope2instance = 3.6

[plone]
# For more information on this step and configuration options see:
# http://pypi.python.org/pypi/plone.recipe.plone
recipe = plone.recipe.plone==3.1


[zope2]
# For more information on this step and configuration options see:
# http://pypi.python.org/pypi/plone.recipe.zope2install
recipe = plone.recipe.zope2install
fake-zope-eggs = true
url = ${plone:zope2-url}

# Use this section to download additional old-style products.
# List any number of URLs for product tarballs under URLs (separate
# with whitespace, or break over several lines, with subsequent lines
# indented). If any archives contain several products inside a top-level
# directory, list the archive file name (i.e. the last part of the URL,
# normally with a .tar.gz suffix or similar) under "nested-packages".
# If any archives extract to a product directory with a version suffix, list
# the archive name under "version-suffix-packages".
[productdistros]
# For more information on this step and configuration options see:
# http://pypi.python.org/pypi/plone.recipe.distros
recipe = plone.recipe.distros
urls =
nested-packages =
version-suffix-packages =

[instance]
# For more information on this step and configuration options see:
# http://pypi.python.org/pypi/plone.recipe.zope2instance
recipe = plone.recipe.zope2instance
zope2-location = ${zope2:location}
user = admin:admin
http-address = 8080
#debug-mode = on
#verbose-security = on
# If you want Zope to know about any additional eggs, list them here.
# This should include any development eggs you listed in develop-eggs above,
# e.g. eggs = Plone my.package
eggs =
${buildout:eggs}
${plone:eggs}

# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =

products =
${buildout:directory}/products
${productdistros:location}
${plone:products}

[zopepy]
# For more information on this step and configuration options see:
# http://pypi.python.org/pypi/zc.recipe.egg
recipe = zc.recipe.egg
eggs = ${instance:eggs}
interpreter = zopepy
extra-paths = ${zope2:location}/lib/python
scripts = zopepy

Der Kern ist die plone.recipe.plone Rezept, für alte Plone verwendet.


1 für die Antwort № 2

Benutzen Plock-Stifte:

Z.B.:

[buildout]
extends = https://github.com/plock/pins/blob/master/plone-3-1