On Sat, Mar 10, 2018 at 01:19:06PM +0000, Stuart Henderson wrote:
> On the other hand I realise it can make it harder to spot warnings in
> build output when building things by hand and I wouldn't mind having
> it controllable via a mk.conf "user settings" variable. Not necessarily
> specific to Go, this could be used in other places too. Something like
> a "PORTS_QUIETBUILD = Yes" variable perhaps?

As far as I can see, the main problem is when you try to fix some port,
and you look at a build system you haven't touched in ages, and you have
to figure out again how to do those things.

There are two possible approaches:
- tell people to document the flags that make sense for this build system
somewhere (and how to pass them thru)
- have some more setup for ports globally, so that you can turn them on.

I *think* that both mechanisms would be useful.

I wouldn't say no  to having a somewhat normalized "cheat sheet" for things
we often need to do in ports...

Reply via email to