svn commit: r531949 - in head/devel: . libuInputPlus

[Alexey Dokuchaev]

On Sat, Apr 18, 2020 at 05:49:43PM +1000, Kubilay Kocak wrote:
> On 18/04/2020 5:10 pm, Alexey Dokuchaev wrote:
> > On Sat, Apr 18, 2020 at 06:28:06AM +0000, Baptiste Daroussin wrote:
> > > I never understood why portname should be lowercase if upstream considers
> > > it should not, there are precedent of mixed case (actually respecting
> > > upstream will).
> > 
> > For the same reasons we don't have `www/Firefox', `databases/PostgreSQL',
> > etc.  It does not look unixish.  There are few special cases when it is
> > indeed desirable to use 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.
> 
> The Python example is in fact actually an example for the opposite.

Well, what I was saying there is that Python ports are distinctive, large
group of ports that may prefer to follow some specific naming convention.
Perhaps I should've just mentioned CPAN.

> The reason we lower-case as a policy in Python is to reduce human,
> contributor, maintainer, committer error by reducing/removing the impedance
> mismatch between the case insensitivity upstream vs case sensitivity in
> ports.

Awesome, so you guys also follow the default sane convention.  That's good.

./danfe