Date: Sat, 18 May 2019 13:18:04 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Jason Bacon <bacon4000@gmail.com> Cc: "Jason W. Bacon" <jwb@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r501873 - in head/biology: . gemma gemma/files Message-ID: <20190518131804.GA12903@FreeBSD.org> In-Reply-To: <205369ac-7666-0d45-7f76-a473915a0eb9@gmail.com> References: <201905171445.x4HEjKE4084764@repo.freebsd.org> <20190518102522.GA45838@FreeBSD.org> <205369ac-7666-0d45-7f76-a473915a0eb9@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > (which in this instance eliminates the need for GH_PROJECT). Setting GH_PROJECT is perfectly normal in this case. > It's not consistent, though, which bugs me a little: [...] > > It would be nice if we either had a clear convention about PORTNAME > or the pkg command were universally agnostic about case. Or we could simply follow Unix predilection to lowercase and stop worrying about these issues. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190518131804.GA12903>