[MacPorts] #38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable
#38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- The `-d` flag implies that the user wants additional information, and passing `--disable-silent-rules` to most configure scripts usually makes the make process print additional information. Of course we'd probably want to test this first so we don't end up with something like the situation with how `qmake` doesn't recognize the `--disable-dependency- tracking` flag. -- Ticket URL: <https://trac.macports.org/ticket/38378> MacPorts <http://www.macports.org/> Ports system for OS X
#38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: invalid | Keywords: Port: | --------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) * status: new => closed * resolution: => invalid Comment: Nah. MacPorts can't know what ports would support that option and what ports would complain. All ports that support --disable-dilent-rules should use it unconditionally. File bugs for individual ports. We've already done this in many ports. -- Ticket URL: <https://trac.macports.org/ticket/38378#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: invalid | Keywords: Port: | --------------------------+-------------------------------- Comment (by larryv@…): Furthermore, this behavior would cause a Heisenberg-esque scenario in which `main.log` changes depending on whether it was observed during its creation. -- Ticket URL: <https://trac.macports.org/ticket/38378#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: invalid | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…):
File bugs for individual ports. We've already done this in many ports.
Are there tickets I could look at that have been filed in the past for individual ports that you've already done this for? -- Ticket URL: <https://trac.macports.org/ticket/38378#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: invalid | Keywords: Port: | --------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:3 egall@…]:
Are there tickets I could look at that have been filed in the past for individual ports that you've already done this for?
I don’t think anyone’s ever filed a ticket about it, but there are currently 88 portfiles containing `--disable-silent-rules`. {{{ port file all | sort -u | xargs grep -le --disable-silent-rules }}} -- Ticket URL: <https://trac.macports.org/ticket/38378#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38378: Using port's -d flag should pass --disable-silent-rules to configure.args when applicable --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: invalid | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:3 egall@…]:
File bugs for individual ports. We've already done this in many ports.
Are there tickets I could look at that have been filed in the past for individual ports that you've already done this for?
I meant: we've already added `configure.args --disable-silent-rules` or equivalent (like `build.args V=1`) to many ports to solve this problem. 44 portfiles matching `V=1`: {{{ port file all | sort -u | xargs grep -Ele '[[:space:]]V=1' }}} The cmake portgroup does this automatically also. One ticket that's still open is #38234. -- Ticket URL: <https://trac.macports.org/ticket/38378#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts