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 14:23:44 UTC
On Sun, Nov 16, 2025 at 05:03:13PM +0300, Max Brazhnikov wrote:
> On Sun, 16 Nov 2025 11:26:55 +0000 Rene Ladan wrote:
> > WWW is a variable, just like any other variable in Makefile, and Makefile is
> > a machine-readable file, unlike e.g. pkg-descr. You cannot humanly read the
> > value of MASTER_SITES either.
>
> I do not need human readable MASTER_SITES: because it is not a full url to
> the source tarball anyway and because 'make fetch' does the job.
I find myself looking at this output for debugging occasionaly.
>
> On the contrary, plain url in WWW is quite handy, you can open the website
> without executing 'make -VWWW'.
So you solved your own problem.
>
> Rene, out of curiosity, what problem are you solving by replacing for example
> https://codeberg.org/rene0/radio_datetime_analyzer
> with
> https://codeberg.org/rene0/${PORTNAME}
> in misc/radio_datetime_analyzer/Makefile?
>
Keeping WWW and PORTNAME synchronized, for example. I could even imagine PORTNAME
being derived from the port directory name by default, but that is another
discussion.
> > The Porters Handbook likely predates the move of WWW from pkg-descr to Makefile.
>
> The Handbook is already updated, all examples use plain url.
>
I found one commit referencing WWW, cdc7bf43fe7d33f904b6d78eef466bc25e59cb7c
which documented the move from pkg-descr to Makefile but does not favour
either format.
Kind regards,
René