Date: Sat, 18 May 2019 10:45:18 -0500 From: Jason Bacon <bacon4000@gmail.com> To: Alexey Dokuchaev <danfe@freebsd.org>, Jan Beich <jbeich@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org, "Jason W. Bacon" <jwb@freebsd.org> Subject: Re: svn commit: r501873 - in head/biology: . gemma gemma/files Message-ID: <95e5a6e0-94ff-bcf6-ca41-5aa2c4d000c5@gmail.com> In-Reply-To: <20190518141808.GA66822@FreeBSD.org> References: <201905171445.x4HEjKE4084764@repo.freebsd.org> <20190518102522.GA45838@FreeBSD.org> <205369ac-7666-0d45-7f76-a473915a0eb9@gmail.com> <20190518131804.GA12903@FreeBSD.org> <4l5r-g8qj-wny@FreeBSD.org> <20190518141808.GA66822@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-05-18 09:18, Alexey Dokuchaev wrote: > On Sat, May 18, 2019 at 04:03:48PM +0200, Jan Beich wrote: >> Alexey Dokuchaev <danfe@freebsd.org> writes: >>> On Sat, May 18, 2019 at 08:09:45AM -0500, Jason Bacon wrote: >>>> Ultimately I chose to follow the pattern of lowercasing the port >>>> directory (except for special cases like perl and cran) and matching >>>> the case of PORTNAME with upstream >>> Vast majority of upstream names use mixed case (most common is first >>> capital letter), but we and GNU/Linux people don't do that: look at >>> package names of Firefox, DeaDBeeF, PostgreSQL, etc. >> - DeaDBeeF installs bin/deadbeef, built from deadbeef-0.7.2.tar.bz2 >> - Firefox installs bin/firefox, built from firefox-67.0.source.tar.xz >> - PostgreSQL installs libraries under lib/postgresql + include/postgresql, >> built from postgresql-11.3.tar.bz2 > Ditto for this port (bin/gemma). But that's a minor thing compared to > general preference in Unix towards lowercase names (binaries, users, > header files, etc.) which naturally extends to package names as well. > > Things should be consistent. Mixed case jeopardizes this consistency. > > ./danfe I'm not motivated by arguments about stylistic preferences, but given the current behavior of pkg, there's a pragmatic issue at-hand. In some pkg commands, the user must match the case of PORTNAME exactly, while in others any mixture of case will work. This is a source of confusion and a nuisance I don't want to impose on users of my ports. I previously fell on the side of matching upstream based partly on the idea that pkg is case-insensitive, which I later discovered is only partially true. With that in mind, I would lean toward lowercasing PORTNAME (except where there is a clear convention, as in p5 and CRAN) unless pkg someday becomes fully case-insensitive, which would reduce the issue to a matter of style. I'm not sure if there are practical reasons that pkg is case-sensitive for some subcommands, but I think it would be more user-friendly to let the user just type everything in lowercase. -- Earth is a beta site.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95e5a6e0-94ff-bcf6-ca41-5aa2c4d000c5>