Re: git: b7f05445c00f - main - Add WWW entries to port Makefiles

Am 08.09.22 um 12:51 schrieb Dmitry Marakasov:
> Why weren't all urls moved to WWW? For my ports, if there were multiple
> WWW's, all of them important and thus all of them should be moved to
> WWW=. Is there a policy which disallows multiple URLs in WWW?

The contents of the WWW variable are made available in the INDEX
and in the package manifests.

If multiple lines starting with "WWW:" were present in pkg-descr,
then only the URL from the first line was used for that purpose.

But there were quite a number of ports that added a generic
framework URL (e.g. to rubyonrails.org), and the order of WWW:
lines was not always correct (e.g. with some less important URL
in the first line).

All URLs have been preserved, either in the Makefile or in the
pkg-descr file. If the one in the Makefile is not the one you
want to be copied into the INDEX, then put another one in.

No decision has been made whether more than URL may be defined
in WWW, but in that case the order of entries becomes arbitrary,
again, and it will be impossible to identify the most relevant
URL from its presence in the WWW variable.

In ports you maintain I see additional URLs only referencing the
repository directory where a port is maintained (e.g. on GitHub),
and only in a very small fraction of your ports.

There generally is one official project website and other relevant
information is linked to that starting point.

The only exception appears to be https://mg.pov.lt/objgraph/ and
that URL is easily found on the website in the WWW field of that
port's Makefile.

I really do not see your point. It is hard enough to have a single
valid URL in the WWW field of each port, and I plan to add a tool
that tests for stale URLs. Having multiple URLs in WWW instead of
the one that is most relevant of a prospective user of the package
will lessen the value of this information, IMHO.

Regards, STefan