Date: Mon, 10 Mar 2014 07:24:23 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Emanuel Haupt <ehaupt@FreeBSD.org> Cc: Mathieu Arnold <mat@FreeBSD.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r346114 - head/devel/p4.el Message-ID: <20140310072423.GC11693@FreeBSD.org> In-Reply-To: <20140226123420.f5c0d0ff40b404a70334da4b@FreeBSD.org> References: <201402260657.s1Q6vEsH059562@svn.freebsd.org> <BEE32AF42CDC7ED09B7234F0@atuin.in.mat.cc> <20140226123420.f5c0d0ff40b404a70334da4b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 26, 2014 at 12:34:20PM +0100, Emanuel Haupt wrote: > Mathieu Arnold <mat@FreeBSD.org> wrote: > > Taking one amongst many, the current practice is to mute the MKDIR > > and not mute commands that install files. Would you mind respecting > > that in the future ? +1. :) > This is just a matter of opinion. I've always preferred to see what is > being installed or what direcories are being created. Even the example > in the PHB doesn't mute the mkdir. Unless this gets correcte in the PHB > I won't change this. To be fair to Emanuel: our Ports Collection has a long tradition of muting mkdir's; I cannot give a definitive answer to why, but I guess it does not add too much of debug info (as something almost always goes into that dir, and install commands should be vocal of course) yet clutters logs a bit at the same time. That said, I believe that better words to describe the best practice would be "do not mute installation commands (inc. cp/cpio-based); mkdir's can be muted unless you prefer them being vocal as well". ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140310072423.GC11693>