git: 30e6befe38aa - main - suitesparse-btf: new port for the module BTF of SuiteSparse

[Alexey Dokuchaev]

On Sat, Jun 05, 2021 at 07:02:48PM +0200, Thierry Thomas wrote:
> ...
> Well, I used for $PORTNAME the naming scheme of upstream. This is also
> the names of the directories after the tarball has been extracted.
> 
> But for origin/dir names I used lowercase, as the porter's handbook
> recommends. Isn't it the best solution?

Not really, no.  It does not look unixish.  There are few special cases
when it is indeed desirable to use upper/mixed cased names, e.g. CPAN
packages, Python modules, those things with established naming convention
of their own, when we bring lots of them to our ports and want to stay
more or less consistent with popular GNU/Linux distributions, but those
are isolated groups.

For some random unattached port it's almost always better tolower() it.
We're Unix, and lowercase is preferred by default.  This tradition is
commonly seen throughout entire Unix heritage and is omnipresent, be it
login names, hier(7), or most APIs.  This naturally applies to port and
package names.  Please don't break this consistency.

./danfe