[89444] trunk/dports/databases/libgda5/Portfile

Daniel J. Luke dluke at geeklair.net
Mon Jan 30 10:21:19 PST 2012


On Jan 30, 2012, at 12:36 PM, Wahlstedt Jyrki wrote:
> On 30.1.2012, at 19.34, Ryan Schmidt wrote:
>> On Jan 30, 2012, at 11:32, Wahlstedt Jyrki wrote:
>>> On 30.1.2012, at 1.26, Dan Ports wrote:
>>>> On Sun, Jan 29, 2012 at 12:28:04PM -0600, Ryan Schmidt wrote:
>>>>> I'm still really not comfortable with this strategy. Any user selecting a variant should get the same result; it should not matter what existing versions of other ports they have installed.
>>>> 
>>>> In particular, this will probably not work right if installing a binary
>>>> archive from the buildbot or elsewhere. That package will be linked
>>>> against whatever library version the build system had installed
>>>> (presumably the default) rather than the one on the user's system.
>>> 
>>> So, naming conventions change, and unfortunately there is no smooth way to move to the new scheme!?
>> 
>> The maintainer should supply legacy compatibility variants for a year, or whatever period of time is deemed necessary to allow most users to have upgraded.
>> 
> Ok,
> so if I restore the old "with_" variants, it should be ok?


no, your +bdb variant is the thing that's really broken. You can have a +bdb variant, but it should just choose one version of bdb to depend on (as the default). You can have other +bdb variants that choose other versions.

Everyone who installs foo +bdb should end up with foo linked to the same version of bdb.

It might make sense to have +bdbXY (where XY is the bdb version) for each one that works/that you want to support and have one be a default variant.

--
Daniel J. Luke                                                                   
+========================================================+                        
| *---------------- dluke at geeklair.net ----------------* |                          
| *-------------- http://www.geeklair.net -------------* |                          
+========================================================+                        
|   Opinions expressed are mine and do not necessarily   |                          
|          reflect the opinions of my employer.          |                          
+========================================================+





More information about the macports-dev mailing list