Re: Why would you use make show rather than make -V in ports?

2017-12-22 Thread Marc Espie 
On Fri, Dec 22, 2017 at 10:57:27PM +, Thomas Levine wrote:
> The normal port Makefile includes this "show" target.
> 
>   $ grep -A3 ^show: /usr/ports/infrastructure/mk/bsd.port.mk
>   show:
>   .for _s in ${show}
>   @echo ${${_s}:Q}
>   .endfor
> 
> Why would one use it rather than make -V?

make -V doesn't expand variables recursively

Won't change it, because it might break stuff that depends on it,
and also, because it could sometimes be useful as it.

Re: Why would you use make show rather than make -V in ports?

2017-12-22 Thread Vadim Zhukov 
2017-12-23 1:57 GMT+03:00 Thomas Levine <_...@thomaslevine.com>:
> The normal port Makefile includes this "show" target.
>
>   $ grep -A3 ^show: /usr/ports/infrastructure/mk/bsd.port.mk
>   show:
>   .for _s in ${show}
>   @echo ${${_s}:Q}
>   .endfor
>
> Why would one use it rather than make -V?

The "show" gives you expanded value when -V gives raw one. Just assign
"foo=$bar" in Makefile and see what happens in both cases.

--
  WBR,
  Vadim Zhukov

Why would you use make show rather than make -V in ports?

2017-12-22 Thread Thomas Levine 
The normal port Makefile includes this "show" target.

  $ grep -A3 ^show: /usr/ports/infrastructure/mk/bsd.port.mk
  show:
  .for _s in ${show}
  @echo ${${_s}:Q}
  .endfor

Why would one use it rather than make -V?