Date: Mon, 04 Jan 2016 11:32:25 -0500 From: "Mikhail T." <mi+thun@aldan.algebra.com> To: koobs@FreeBSD.org, python@FreeBSD.org Subject: Re: lowercase requirement for py-ports (Re: svn commit: r405240 - in head/devel: . py-PyLD) Message-ID: <568A9E99.4050303@aldan.algebra.com> In-Reply-To: <568A9827.4070505@FreeBSD.org> References: <201601041351.u04Dp2jq004769@repo.freebsd.org> <568A798E.8050308@FreeBSD.org> <568A8C28.7080803@aldan.algebra.com> <568A8E6C.7010000@FreeBSD.org> <568A95A6.8060002@aldan.algebra.com> <568A9827.4070505@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04.01.2016 11:04, Kubilay Kocak wrote:
> No discussion archive
Well, if it is not a result of a discussion arriving to a consensus,
then, perhaps, the rule is not as hard, is it? What are you reasons
behind it?
> also PyPI is case insensitive
Ah, good to know. Perhaps, that's because Python has to work on OSes
with case-insensitive filesystems. But FreeBSD is not among those...
> FWIW, some of the current practice also includes arbitrarily changing
> the names/versions, missing prefixes/suffixed (causing known conflicts),
> among other non-standard things.
I agree, that /these/ things are best avoided. Mixed-case portnames,
however, are not so obviously wrong.
> My guess is also that multi-case ports are in the minority.
It is a /substantial/ minority. Analyzing the INDEX-10 here, I get:
% awk -F\| '$1 ~ /.*[A-Z].*/ {upper++} {total++} END {print upper "
of " total " ports have capital letter in name"}' INDEX-10
6312 of 25575 ports have capital letter in name
Yours,
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?568A9E99.4050303>