https://github.com/toumorokoshi/yt.recipe.relativeworkaround

A workaround for some buildout behavior that uses absolute paths for the base directory instead of a relative version.
https://github.com/toumorokoshi/yt.recipe.relativeworkaround

Last synced: 8 days ago
JSON representation

A workaround for some buildout behavior that uses absolute paths for the base directory instead of a relative version.

• Host: GitHub
• URL: https://github.com/toumorokoshi/yt.recipe.relativeworkaround
• Owner: toumorokoshi
• License: mit
• Created: 2015-02-09T16:09:04.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2015-03-06T01:19:03.000Z (almost 10 years ago)
• Last Synced: 2024-10-28T20:05:10.795Z (about 2 months ago)
• Language: Python
• Size: 133 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README
  • License: LICENSE

Awesome Lists containing this project

README

        
# yt.recipe.relativeworkaround

This is a buildout recipe that will fix an annoying with buildout: when the

relative-paths options is turned on, it will still use the absolute path when referencing

the buildout root:

    # buildout.cfg

    [buildout]

    relative-paths = true

    [scripts]

    recipe = z3c.recipe.scripts:scripts

    eggs =

        fabric

    interpreter = python

The result is absloute paths still added in various places:

    $ cat parts/scripts/site.py | grep `pwd`

        '/Users/yusuket/stash/TOOL/shipit'

Run this recipe at the end of your build, and it will do it's best to

correct them to the proper values.