From owner-cvs-all@FreeBSD.ORG Wed Mar 19 09:18:59 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1033) id E51DF106566C; Wed, 19 Mar 2008 09:18:59 +0000 (UTC) Date: Wed, 19 Mar 2008 09:18:59 +0000 From: Alexey Dokuchaev To: Pav Lucistnik Message-ID: <20080319091859.GA56200@FreeBSD.org> References: <200803180100.m2I10QTD070047@repoman.freebsd.org> <20080318193855.0439b197.stas@FreeBSD.org> <20080318181546.GA10903@FreeBSD.org> <1205917353.76695.0.camel@pav.hide.vol.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1205917353.76695.0.camel@pav.hide.vol.cz> User-Agent: Mutt/1.4.2.1i Cc: Stanislav Sedov , cvs-ports@FreeBSD.org, ports-committers@FreeBSD.org, cvs-all@FreeBSD.org, Pietro Cerutti Subject: Re: cvs commit: ports/java/eclipseme Makefile distinfo pkg-plist X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2008 09:19:00 -0000 On Wed, Mar 19, 2008 at 10:02:33AM +0100, Pav Lucistnik wrote: > Alexey Dokuchaev p??e v ?t 18. 03. 2008 v 18:15 +0000: > > > Not to mention that -R should've probably be used instead or -r, and we > > generally try not to mute installation of files/links (as opposed to > > dirs). > > Since you mentioned it, I wonder, why you think it's useful to silence > the mkdir calls? This question was raised before several times. When I started working on ports back some n years, I noticed that lots of MKDIR's were muted, while INSTALL_FOO's were not. I thought that this is probably for the same reason why we do not generate a commit message for directory creating in CVS, just for the files. In other words, creating a directory normally followed by some file(s) being put in it, thus MKDIR itself carries less information and probably just making things overly noisy (yet verbose). To tell you the truth, I'm all hands for a policy here. If we decide (like we had decided with patch files naming) upon certain convention, whatever it'll be, I will just follow that. I'd love to see more consistency and order in our Ports Collection. ./danfe