#20002: bugs in vtk-devel Portfile on Tiger -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: dweber@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: Tiger darwin_8 | Port: vtk-devel -------------------------------+-------------------------------------------- Comment(by dweber@…): Oops, let's fix that formatting! When debugging the install process, I often clean out the destroot entirely because of the file copy error. My debug process looks something like: {{{ $ sudo port destroot vtk-devel +huge $ # examine build and destroot, revise Portfile as required $ sudo rm -rf ${workpath}/destroot $ sudo vim ${workpath}/.macports*.state # to remove destroot state $ sudo port -o -k -d destroot vtk-devel +huge }}} The -o option avoids an entire rebuild just because the Portfile changed. Of course, if you change build settings or something, then you may want to rebuild. For the most part, the debug process has to tweak the destroot (vtk usually compiles OK). The -k option is just there to 'keep' the build. I leave it in the command line just in case I change the destroot to an install command (my macports config does a clean after an install). -- Ticket URL: <http://trac.macports.org/ticket/20002#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS