give access to current profile path and base path in section

Bug #767190 reported by Łukasz Nowak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Buildout
New
Undecided
Unassigned

Bug Description

Imagine a situation:

buildout.cfg (on local machine):
[buildout]
extends = http://remote-server/slave.cfg

http://remote-server/slave.cfg
[buildout]
parts = complex

[complex]
recipe = recipe.to.build.crazy.software
source = http://software/vendor/tarball.tgz
patch = patch_repository/important.patch

The patch is published in http://remote-server/patch_repository/important.patch

Currently it will not work, forcing me to download http://remote-server/patch_repository/important.patch.
To not be forced to download I would have to override its location, but then I would need to track remote changes, or in case of many extends, it will make extends unmaintainable.

I'd like to have mechanism, that it would be possible to have a parameter (lets say ${:_profile_base_location_}) in section, which would expand to http://remote-server/ in above example.

So slave.cfg would look like:

[buildout]
parts = complex

[complex]
recipe = recipe.to.build.crazy.software
source = http://software/vendor/tarball.tgz
patch = ${:_profile_base_location_}/patch_repository/important.patch

Which would make it work in being remotely extended (or used) and locally downloaded (with patch_repository/important.patch directory available) cases.

Revision history for this message
Łukasz Nowak (ionowaklukasz) wrote :

Please see attached implementation proposal and test.

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Revision history for this message
Marius Gedminas (mgedmin) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.