On 2011-8-9 06:07 , Bradley Giesbrecht wrote: > > On Aug 8, 2011, at 12:52 PM, Ryan Schmidt wrote: > >> On Aug 8, 2011, at 14:46, Bradley Giesbrecht wrote: >> >>> I thought it was common/suggested that the replaced_by stub port have >>> a dependency on the port that replaced them; >> >> Nope. >> >>> making it likely that "port upgrade outdated" will succeed when the >>> replaced port is depended on by other ports. >> >> If the replaced port is depended upon by other ports, those other >> ports need to be updated to now depend on the replacement. That's the >> responsibility of whoever caused the port to be replaced. > > That can take some time when ports that depend on the replaced_by port > are not maintained by you and are not openmaintainer. Seems reasonable > to accommodate successful upgrades during the transition.
Depending on a port that can't be installed isn't ever going to work. The point at which you should be clearing things with maintainers is before you break their ports by turning one of their dependencies into a stub. - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
