icu 50 and how to identify dependents
ryandesign at macports.org
Mon Feb 11 16:14:49 PST 2013
On Feb 11, 2013, at 17:56, Jeremy Huddleston Sequoia wrote:
> On Feb 10, 2013, at 4:15 PM, Jeremy Huddleston Sequoia wrote:
>> I started a clean build with my patch in https://trac.macports.org/ticket/38010, and so far no issues.
> I build 721 ports in my standard set of installed ports. Of these, 15 had issues building with the la files deleted in my rebuild. In each case, the issue was that the project wasn't declaring a dependency that it was using, and the fix was just to add the missing linkage. Most of the cases involved gnome ports failing to link against gmodule-2.0, but there were a couple others.
Thanks, this is good.
Starting over from no ports installed is a good test, but of course our users will already have ports installed. Are the changes that have already been committed to trunk considered to be a complete solution? Can one upgrade to trunk and install and upgrade ports at will and expect everything to work (with the exception of bugs like the ones you're finding and fixing above)? I got the impression from some of the links that Joshua posted in the ticket that the order in which the flags were removed from packages was important, but the changes in base would seem to remove the flags from every port as it's installed.
More information about the macports-dev