https://github.com/multani/buildout.dumppickedversions-mirror

Mirror of buildout.dumppickedversions' Subversion repository
https://github.com/multani/buildout.dumppickedversions-mirror

Last synced: about 1 year ago
JSON representation

Mirror of buildout.dumppickedversions' Subversion repository

• Host: GitHub
• URL: https://github.com/multani/buildout.dumppickedversions-mirror
• Owner: multani
• Created: 2011-03-26T22:52:04.000Z (about 15 years ago)
• Default Branch: master
• Last Pushed: 2011-03-26T22:54:04.000Z (about 15 years ago)
• Last Synced: 2025-01-23T02:24:55.716Z (over 1 year ago)
• Language: Python
• Homepage: http://pypi.python.org/pypi/buildout.dumppickedversions
• Size: 156 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.txt
  • Changelog: CHANGES.txt

Awesome Lists containing this project

README

          
buildout.dumppickedversions

===========================

Q: What is a buildout extension ?

A: http://pypi.python.org/pypi/zc.buildout#extensions

The problem

-----------

When using a zc.buildout based deployment system you want to be able to 

reproduce the same setup with the same set of egg versions one month later.

Without pinning all eggs the task is impossible.

Solution

--------

``buildout.dumppickedversions`` is a buildout extension that does just that. It

can print or generate a versions.cfg file with all not pinned eggs.

It adds also a comment before each egg picked by zc.buildout as requirment for 

other eggs containing the list of eggs that required it.

buildout.dumppickedversions options

-----------------------------------

dump-picked-versions-file

    A file name you want ``buildout.dumppickedversions`` to write to.

    If not given ``buildout.dumppickedversions`` will dump the versions to the 

    screen.

overwrite-picked-versions-file

    If set to ``true``, ``buildout.dumppickedversions`` will overwrite the file 

    defined in ``dump-picked-versions-file`` if it exists. Defaults to True.