port -f clean should ignore locks on the working tree
This is annoying, to say the least:
chibi:MacPorts steve$ port clean sbcl
Waiting for lock on /opt/local/var/macports/build/_Users_steve_Software_MacPorts_dports_lang_sbcl/work/.macports.sbcl.state
^C
chibi:MacPorts steve$ port -f clean sbcl
Waiting for lock on /opt/local/var/macports/build/_Users_steve_Software_MacPorts_dports_lang_sbcl/work/.macports.sbcl.state
^C
chibi:MacPorts steve$ rm /opt/local/var/macports/build/_Users_steve_Software_MacPorts_dports_lang_sbcl/work/.macports.sbcl.state
chibi:MacPorts steve$ port clean sbcl
---> Cleaning sbcl
chibi:MacPorts steve$
Change History (4)
Component: |
ports →
base
|
Milestone: |
→ MacPorts base bugs
|
Resolution: |
→ wontfix
|
Status: |
new →
closed
|
Milestone: |
MacPorts base bugs →
MacPorts Future
|
Milestone: |
MacPorts Future
|
The lock indicates that another port process is using that file, so if we go ahead and destroy it, it can mess up the other process.