pedroalvarez: So, my understanding is that the blockers for this are 1) that morph complains if it's not in a workspace, and 2) that morph doesn't know where to find definitions when you run morph build if you don't have a workspace (as it hides the path to definitions in a config file)

But if morph doesn't try to understand, you'll get stuck with relative paths forever. We can't have it both ways. Are you happy enough with the potential to make it faster to put up with relative paths?

The use case in question is a distributed development team that wants to use chroots, and wants to be able to update some components once in a while without needing every developer to restart the preparation of their working area from scratch.

Essentially, to do that we'd have to have some way to regenerate the effects of deployment on the client, and since we're running the same operation many times in parallel in differing environments, it is hard to be confident we always get the same result.

Looking through my IRC logs, it appears that the the Task_List page petefoth linked matches current thinking in the area, and all the prior models have been deprecated (as they can be expressed in terms of task lists and tags).

my problem is that I've been using python long enough to get bored and look for the weird tools available in the language; liw-orc has been using python long enough that he's already been through that, and knows which python things are the best compromise between speed, size and readability