Date: Fri, 26 Aug 2011 02:37:16 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: cvs-ports@FreeBSD.org, Joe Marcus Clarke <marcus@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/ports-mgmt/portlint Makefile ports/ports-mgmt/portlint/src portlint.pl Message-ID: <20110826023716.GB68483@FreeBSD.org> In-Reply-To: <20110825230725.00000cfd@unknown> References: <201108212335.p7LNZRtU068978@repoman.freebsd.org> <20110822014003.GB93790@FreeBSD.org> <20110825230725.00000cfd@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 25, 2011 at 11:07:25PM +0200, Alexander Leidinger wrote: > On Mon, 22 Aug 2011 01:40:03 +0000 Alexey Dokuchaev <danfe@FreeBSD.org> > wrote: > > I would probably issue a warning about using the dot in port's name, > > as it looks quite ugly regardless of ".core" thing. With perhaps few > > exceptions like ".el" ports, the rest should have used minus instead > > of the dot. > > The main reason for my request was that there was a commit of such a > file and it triggered a warning in the periodic scripts in a > read-only mount of ports. The periodic scripts check for coredumps and > delete them. I understand that. > I don't understand why you talk about port names here, are you talking > about the change, or are you making a suggestion of checking for dots > in port names? The latter. I meant something like, "since you're here fixing .core issue with periodic scripts, maybe it makes sense to issue warning for any usage of dots in the port names, as doing so 1) makes names look less pretty; 2) introduces inconsistency in a family of ports (see e.g. science/py-obspy*). I am aware that few people care for aesthetic appeal, but I do, hence the suggestion. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110826023716.GB68483>