Re: Literal text WWW in ports Makefile (Was: git: 4bb2e36e912e - main - sysutils/gol: New port: All-in-one log viewer in browser)
- Reply: Max Brazhnikov : "Re: Literal text WWW in ports Makefile (Was: git: 4bb2e36e912e - main - sysutils/gol: New port: All-in-one log viewer in browser)"
- In reply to: Max Brazhnikov : "Re: Literal text WWW in ports Makefile (Was: git: 4bb2e36e912e - main - sysutils/gol: New port: All-in-one log viewer in browser)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 16 Nov 2025 18:19:02 UTC
On 11/16/25 14:08, Max Brazhnikov wrote: > For a group of related ports? Sure. However in this case you'll probably > prefer to set WWW once in some common.mk The problem arises when the maintainer maintains multiple ports, even if those ports are unrelated to each other. When multiple ports are created, for example, 5 Python ports and 5 Golang ports, a pattern is likely to emerge and the code tends to be repetitive, so it is better to repeat much less while taking advantage of variables. > Superfluous 'make -VWWW' is the problem! I know that all you have to do is click on the URL to open it when you have a Makefile open, but honestly, how long does it take to run "make -V WWW"? I use neovim and it takes me a second to run ":!make -V WWW" and open the URL.