> On Jan 21, 2015, at 5:43 PM, René J.V. Bertin wrote: > >>> I've tried changing the version in the +infinality variant, so that for >>> instance port:freetype is at 2.5.4 and port:freetype+infinality at >>> 2.5.4.150101 . That works, but something in MacPorts breaks. I can do `port >>> patch freetype +infinality` to check whether the patches apply correctly, >>> but when I continue with `port configure freetype +infinality` the process >>> continues all the way to the install or until the 1st error. >> >> That sounds like a bug. It would be great if you could open a ticket about >> it and provide a minimal test case. > > I actually considered this approach a rather ugly hack, but apparently it's > not unsupported and supposed to work? > I'll see if I can come up with one, on the backburner.
I don't think we ever intended the version to be changed inside a variant. I would consider it a maintainer error to do so. I don't think the portindex accommodates more than one version per port, and the portindex is used to determine what ports are outdated. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
