On 10/21/11 6:28 PM, Ryan Schmidt wrote: > On Oct 21, 2011, at 20:19, David Evans wrote: >> On 10/21/11 4:29 PM, Ryan Schmidt wrote: >>> On Oct 20, 2011, at 17:35, David Evans wrote: >>>> On 10/20/11 2:41 PM, Ryan Schmidt wrote: >>>>> On Oct 20, 2011, at 15:15, devans wrote: >>>>>> py26-atspi: add license, remove redundant dependency on python26. >>>>> It wasn't particularly redundant, was it? py26-atspi does itself use >>>>> python26, so it was appropriate for py26-atspi to list a dependency on >>>>> python26. >>>>> >>>> By redundant, I meant that, in particular, py26-gtk declares a >>>> dependency on python26 so it is not necessary to do so again. One could >>>> argue that it isn't even necessary to declare python26 in py26-gtk, >>>> since its dependents >>>> py26-cairo and py26-gobject each declare it. >>> No, I disagree with this reasoning. >>> >>> py26-gtk, py26-cairo and py26-gobject each directly use python26, therefore >>> it is proper for each of them to declare a dependency on python26. >>> >>> Imagine there is a bug or change in python26 that requires all dependents >>> to be rebuilt, i.e. to have their revisions increased. You want to be >>> easily able to identify all those ports by grepping the portfiles for >>> ":python26". You don't want to have to go hunting around the dependency >>> chain; it takes forever and you always miss some. We've had this time and >>> time again, for example when gettext or libpng get updated to new major >>> versions. Granted, this problem is easier to imagine when we're talking >>> about shared libraries like gettext or libpng, but I wouldn't say it's out >>> of the question for python. >> I thought we had gotten away from the grepping of ports with commands like >> >> port echo depends:python26 >> >> (which, by the way, correctly reports py26-atspi as depending on >> python26 even with my change). >> >> Its fast and seems to give the desired results. > Ah... I've still been grepping ports, because I seem to have missed the > introduction of that command. It does seem to work... I guess we should > promote the heck out of that command then! It seems to be missing from "man > port" but is in the guide: > > http://guide.macports.org/#using.common-tasks.finddepending > Absolutely, whoever added that command deserves a big attaboy!!
> _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
