#15881: Building foo with target all -------------------------------------+-------------------------------------- Reporter: ryandesign@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: ports | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- Why does the user care that a port is being built "with target all"? {{{ $ port install foo ---> Fetching foo ---> Verifying checksum(s) for foo ---> Extracting foo ---> Applying patches to foo ---> Configuring foo ---> Building foo with target all ---> Staging foo into destroot ---> Installing foo @1.2.3_0 ---> Activating foo @1.2.3_0 ---> Cleaning foo $ }}} The user is not informed of any other minutiae of the build process, for example whether the source was extracted from a bzip2 or a gzip or a zip archive, or whether a particular configure argument was needed, or whether the destroot phase needed to inform the install process of the destroot path via different mechanism. The user doesn't care about all that, nor does he care that the "make" command happened to want the argument "all" passed to it. And if he does, he can use the verbose or debug switches. So can we please remove "with target <whatever>" from the "Building" info line? -- Ticket URL: <http://trac.macports.org/ticket/15881> MacPorts <http://www.macports.org/> Ports system for Mac OS