How to fix "broken ports"?

[Bradley Giesbrecht]

On May 26, 2012, at 6:22 AM, Marko Käning wrote:

> On May 26, 2012, at 3:09 PM, Clemens Lang wrote:
>> 
>> This kind of output is pretty much useless, because it doesn't tell you
>> why the file was marked as broken.
> I know, Clemens. Since I saw already with "-d" what caused the breaking I didn't think it would be needed to append the whole list, since I wanted to focus more on automoc and qt4-mac...
> 
>> If that is the case and automoc links against qt4-mac it's obvious why
>> rev-upgrade marks it as broken (it's dependency library is missing). In
>> the first rebuild step any missing dependencies for a broken port should
>> be installed, fixing this problem.
> Yes, I see your point. But the problem is that automoc is installed and active
> ---
> $ port installed automoc
> The following ports are currently installed:
>  automoc @0.9.88_3 (active)
> $ port deps automoc
> Full Name: automoc @0.9.88_3
> Build Dependencies:   cmake, pkgconfig
> Library Dependencies: qt4-mac
> $ port installed qt4-mac
> None of the specified ports are installed.
> ---
> without qt4-mac installed.


Could changes in the kde portgroups explain this?

svn diff -r63197 dports/_resources/port1.0/group/kde4-1.0.tcl

Where qt4-mac-devel could have satisfied a dependency and then later the portgroup was changed?


Regards,
Bradley Giesbrecht (pixilla)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2763 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120527/84a3367b/attachment.bin>