I want to make a change to a port that requires a change in another port. The ports are gdal and proj. The current versions of proj and gdal have problems such that gdal cannot dynamically link proj. In order for dynamic linking to work, I need to upgrade proj to version 4.5.0. I've already submitted a patch that upgrades gdal statically links proj. I'd like to change the gdal patch to dynamically link proj but the update to proj will have to go in simultaneously. What are the chances of that happening? Is there a way to make that happen? Is there a mechanism to make dependencies based on version? Thanks, Sean
On Apr 7, 2007, at 9:55 AM, Sean Fulton wrote:
I want to make a change to a port that requires a change in another port.
The ports are gdal and proj. The current versions of proj and gdal have problems such that gdal cannot dynamically link proj. In order for dynamic linking to work, I need to upgrade proj to version 4.5.0.
I've already submitted a patch that upgrades gdal statically links proj. I'd like to change the gdal patch to dynamically link proj but the update to proj will have to go in simultaneously.
What are the chances of that happening? Is there a way to make that happen?
You're the maintainer on both, right? So it's easy - just make sure that the trac tickets or committer you ping know that they need to go in together, they won't appear in anyone's tree until the next rsync run, so they don't have to be the same commit, just close to each other in time.
Is there a mechanism to make dependencies based on version?
Nope (not yet, anyway). -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
participants (2)
-
Daniel J. Luke
-
Sean Fulton