#13918: port activate returns 0 exit code even when unsuccessful -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.7.0 Keywords: | Port: -------------------------------------+-------------------------------------- Comment(by ryandesign@…): Replying to [comment:6 blb@…]:

We have both -x and -p, which basically do opposite things, and is therefore really confusing. I say what -x does should be the default for port (stop when an error happens) and keep -p for those (few?) who really want port to continue even when it encounters an error. Sounds good. I have gotten in the habit of manually typing the "-x" option every time I install or upgrade a port.

I do use the "-p" option on occasion as well. Sometimes I want to "port clean all" to clean out partial build attempts. Sometimes one of the partial build attempts will have been done as root. (My install is non- root so most software is not built as root.) Those that were built as root will interrupt "port clean all" unless I use "-p": {{{ $ port clean osx2x mysql5 portaudio ImageMagick ---> Cleaning osx2x /mp/var/macports/build/_Users_rschmidt_macports_dports_databases_mysql5/work/.macports.mysql5.state is not writable - check permission on port directory Error: Status 1 encountered during processing. $ port -p clean osx2x mysql5 portaudio ImageMagick ---> Cleaning osx2x /mp/var/macports/build/_Users_rschmidt_macports_dports_databases_mysql5/work/.macports.mysql5.state is not writable - check permission on port directory Error: Status 1 encountered during processing. ---> Cleaning portaudio ---> Cleaning ImageMagick $ }}} -- Ticket URL: <http://trac.macports.org/ticket/13918#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS