Being in a soon-to-be-deactivated directory causes port to error

[blb@…]

This is an extremely esoteric bug, but for tracking purposes (while sitting in /opt/local/lib/erlang, which is exclusively from the erlang port):

$ sudo port deactivate erlang
Password:
--->  Deactivating erlang
cd
couldn't change working directory to "/opt/local/lib/erlang": no such file or directory
    while executing
"cd $savedir"
    (procedure "foreachport" line 17)
    invoked from within
"foreachport $portlist {
        if { [catch {portimage::deactivate $portname [composite_version $portversion [array get variations]] [array get option..."
    (procedure "action_deactivate" line 6)
    invoked from within
"$action_proc $action $portlist [array get global_options]"
    (procedure "process_cmd" line 86)
    invoked from within
"process_cmd $remaining_args"
    invoked from within
"if { [llength $remaining_args] > 0 } {

    # If there are remaining arguments, process those as a command

    # Exit immediately, by default, unless..."
    (file "/opt/local/bin/port" line 3225)

[ryandesign@…]

It's not so esoteric IMHO. I often find myself in a port's work directory when I try to install it again, which deletes the work directory, so when the port command is done, the above error occurs.

[toby@…]

Milestone MacPorts base bugs deleted

[jmr@…]

I think this may have been fixed with the gsoc08-privileges merge?

[blb@…]

It no longer errors out, but does leave you in that now-removed directory. Probably not worth it trying to detect that case and to cd someplace else, so I call it fixed.