Python ports providing GNOME bindings

[Jordan K. Hubbard]

On Apr 15, 2010, at 5:23 PM, Ryan Schmidt wrote:

> I remain unconvinced the "bug" should be fixed. If port A depends on port X+Y and port B depends on port X+Z then what? What if X's variants +Y and +Z conflict?

Aha!  This is why I remain convinced that software should depend directly on the depot locations of its dependencies, in which case port X+Y and port X+Z can co-exist just fine on the same system.   I also suspect that it's time that we took a good, hard look at what it means to be "activated" in both the current and high-level senses of the word.  There are lots of ways of putting stuff into a process' filesystem namespace these days, only one of which involves actually making the global filesystem changes in question, the needs of MacPorts and the needs of process sandboxing may also intersect in various interesting ways.  I think there's more architecture in place in the OS to fake things out such that we *don't* have to permute all the configuration / build settings to point at all those depot locations, either, which has always been a sticking point.

- Jordan