David Pratt wrote:
Hi Jim. I think ${name} or ${part} would be good.

Sorry for poor example. baz in prev example could be a version or other differentiating information to form a path name. Here's a better example though there is many places this could be used.

extra-options = --datadir=${software:prefix}/share/${name}

BTW, can you think of anyway to work around the first issue for buildout part. For substitution to work, could buildout part have its own dict as a data source for substitution prior to files being configured as a special case). Then after config do the routine substitution. So you could have something like the following. Thing is this is a pretty small example and when you get a number of configurations going with long paths, well its sort of looks ugly too, especially if you are using urls or paths that may be the same.

Sorry, should have clarified that it is the scenario with the long long paths or urls that is undesirable. The first case below represents what I'd rather see which keeps it fairly clean.

develop = .
parts = somepart anotherpart
etc = p1=/somewhere/in/my/filesystem
extends = ${etc:p1}/bar.cfg

contrast this with the following without the prefixes:

develop = .
parts = somepart anotherpart
extends = /somewhere/in/my/filesystem/bar.cfg


Jim Fulton wrote:

On Feb 14, 2008, at 5:59 PM, David Pratt wrote:
One other thing that I have not yet seen is using the part name within the part which would be useful. Something like:

baz = bar
log = /some/path/${foobar:?}-${foobar:baz}.log

I don't follow the example.  I can thing of perhaps similar examples:

  log = /some/path/${name}-something.log

where ${name} refers to the part name. I definitely want to do something like this. I'm not sure what syntax should be used.


Jim Fulton
Zope Corporation

Zope3-users mailing list

Zope3-users mailing list

Reply via email to