On Feb 22, 2007, at 6:15 AM, Weissmann Markus wrote:
The problem I see here is, that there is code that runs with 2.5 but not with 2.4 (and vice versa). Therefore we would at least need a mechanism for also allowing the "cheap" duplicate ports (for 2.4 and 2.5) as there will be modules that work with 2.4 in version A and only with 2.5 with version B. Could we perhaps somehow specify two port definitions in one Portfile? Or find a good mechanism to include the common parts of two Portfiles from a shared third file? Thoughts?
The portgroup code could activate a version-specific variant after detecting the macports installed python version. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+