Re: Literal text WWW in ports Makefile

On Mon, Nov 17, 2025 at 12:12 PM Chris <i.h8.git@bsdforge.com> wrote:

> On 2025-11-15 12:21, Max Brazhnikov wrote:
> > On Sat, 15 Nov 2025 19:43:26 +0100 Zsolt Udvari wrote:
> >> On Sat, Nov 15, 2025 at 09:16:30PM +0300, Max Brazhnikov wrote:
> >> > WWW also was a literal text when it just migrated to Makefile. Why it
> should
> >> > be obfuscated now? No difference for the make, but less convenient
> for humans:
> >> > plain text url can be opened from the editor without running the make.
> >>
> >> The github, gitlab and pear set a WWW (if it isn't defined in Makefile)
> so
> >> you can't open the url without running make. If you want see plain text
> >> url should remove these definitions from Mk/bsd.sites.mk and
> >
> > I'm ok with this, framework may set WWW for ports, and ports can
> redefine it
> > if needed. But if WWW is explicitly set in the Makefile it should be
> plain
> > url.
>
> If either is possible. Why should it not be what is easiest or most
> efficient
> for the
> Maintainer/Developer at the time?
>

Because it should be what is most helpful and useful for end-users, not the
maintainer.

It's a worse experience for the end-user, doesn't actually save the
maintainer any time, and really the only benefit is that the port needs
fewer changes if the name of the program suddenly changes, which occurs
once every never.

We are not the customer, nor is make(1).


-- 
Adam Weinberger
adamw@adamw.org // adamw@FreeBSD.org