Problem installing KDE/Amarok

Hal Vaughan hal at halblog.com
Wed Jun 24 15:18:45 PDT 2009


On Jun 24, 2009, at 6:02 PM, Ryan Schmidt wrote:

> On Jun 24, 2009, at 16:47, Hal Vaughan wrote:
>
>> I figured they'd be lost if I had to kill the terminal.  Of course,  
>> I'm not 100% sure that this is the issue.  For all I know, the  
>> process could have been okay and it could be something else that  
>> crashed it.  (Come to think of it, there was an ssh connection, but  
>> it's a program I'm always running in the b.g.)  I figure in worst  
>> case, since it's the first thing I'm installing, I could wipe out  
>> any KDE directory in Applications and just wipe all of /opt,  
>> reinstall MacPorts and restart.
>>
>> Is there any place else KDE would store files that I'd have to  
>> clear out if I do that?
>>
>>> After restarting Terminal or the computer, you can try again. You  
>>> can use the "-d" flag ("port -d install amarok") to get a lot more  
>>> information printed out. This will let you see what exactly a port  
>>> was doing if and when it gets hung up. On the other hand, the vast  
>>> quantity of output you will get means you will very likely miss  
>>> any "you must do this after installing the port"-type messages  
>>> that some ports print.
>>
>> I was also going to see if I could find a list somewhere of all the  
>> messages from KDE.  It looks like each package is giving me the  
>> same message at the start and the end.
>>
>> I'll most likely wipe out /opt and just start clean, since I don't  
>> have any other packages done with MacPorts yet.  I don't mind  
>> letting it rebuild qt overnight.
>
> If you want to do that, you should follow the uninstall instructions  
> shown here:
>
> http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts

How is that at dealing with partially installed packages, like the kde  
one I'm dealing with?


Hal


More information about the macports-users mailing list