upgrade exept certain ports

[Barrie Stott]

On 19 Mar 2012, at 14:27, Ryan Schmidt wrote:

> On Mar 19, 2012, at 09:02, Barrie Stott wrote:
> 
>> On 19 Mar 2012, at 01:10, Ryan Schmidt wrote:
>> 
>>> Personally I just run "port outdated" and then individually upgrade the specific ports I want to upgrade. If it starts building something I didn't want it to build, I cancel it. (For example, I'm not ready to upgrade to Subversion 1.7 yet, so if, when upgrading some other port, it starts trying to upgrade subversion, I cancel it.)
>> 
>> This is slightly off-topic but how does one 'cancel' an upgrade or an install?
> 
> If using the port command in a terminal, interrupt by pressing Control-C. (This applies to any command-line program, not just "port".) If using a GUI, consult its documentation. It's important to consider what phase of a port MacPorts is working on, to decide whether interrupting it at that moment is a good idea. Individual ports may deviate, but for a generic port foo:
> 
> * Fetch: interrupting ok; resuming will restart incomplete downloads the beginning
> * Verify checksums: interrupting ok
> * Extract, Patch, Configure: interrupting ok, but clean before trying again
> * Build: interrupting ok; resuming should pick up building where it left off
> * Destroot: interrupting ok; resuming might not work; if not, remove "$(port workpath foo)/destroot" or clean and try again
> * Install: don't interrupt; I don't know exactly what happens
> * Activate: don't interrupt; unregistered files might end up getting installed (if you do interrupt, you might have to "sudo port -f activate foo" next time)
> * Clean: don't interrupt; files might not get cleaned up (if you do interrupt, run "sudo port clean foo" yourself)

I'm really grateful for that, Ryan. I've always been frightened of interrupting an install or upgrade because of the unknown havoc I might cause and have to live with. In future, I'll be watching the stages as they pass by with your list in mind.

Thanks again,

Barrie.