From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCH] gnu: Fix load-extension path in packaging of guile-ncurses. Date: Sun, 15 Jan 2017 19:11:58 -0500 Message-ID: <87pojnj229.fsf@netris.org> References: <1482169820-2043-1-git-send-email-jmd@gnu.org> <1482169820-2043-2-git-send-email-jmd@gnu.org> <87lgvb9ii1.fsf@netris.org> <20161220110331.GA20543@jocasta.intra> <20161221093656.400cd7cd@scratchpost.org> <20161221095646.GA6917@jocasta.intra> <4b79e545-7ea6-3b6c-3a48-f5f1d6b1da3c@tobias.gr> <20161222082001.GA3545@jocasta.intra> <87mvflz683.fsf@netris.org> <20161224170221.GA26932@jocasta.intra> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57353) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cSuuJ-0005LR-8G for guix-devel@gnu.org; Sun, 15 Jan 2017 19:12:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cSuuF-00062g-68 for guix-devel@gnu.org; Sun, 15 Jan 2017 19:12:19 -0500 Received: from world.peace.net ([50.252.239.5]:46882) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cSuuF-00062W-13 for guix-devel@gnu.org; Sun, 15 Jan 2017 19:12:15 -0500 In-Reply-To: <20161224170221.GA26932@jocasta.intra> (John Darrington's message of "Sat, 24 Dec 2016 18:02:21 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: John Darrington Cc: guix-devel@gnu.org John Darrington writes: > On Sat, Dec 24, 2016 at 10:39:40AM -0500, Mark H Weaver wrote: > John Darrington writes: > > > We can argue about this till we're blue in the face. > > > > But on a pragmatic level, Mark's question demonstrates perfectly > > that our current system is lacking. > > No it doesn't. Our convention, taken from the GNU coding standards, is > that the rationale for non-obvious code belongs in the code itself. My > question demonstrates perfectly that you should have done _that_. > > For what it's worth, I agree that there are some cases where adding > rationale comments to the code itself doesn't make sense (e.g. when > removing code), but this is clearly not one of those cases. > > > > Having it in the commit message would certainly have avoided me > > > having to explain the situation to Mark too. > > > > Perhaps. I doubt it. I can't speak for Mark, but most confusion > > seemed to stem from the commit message's accuracy, not its length. > > Yes, exactly. > > To be honest, I find it unsettling that after all that has been pointed > out in this thread, you still seem unwilling to admit that you made any > mistake here. > > Have you looked at the build log, and specifically the part of the build > log that corresponds to your 'fix-libguile-ncurses-file-name' phase? > > Have you noticed how the 'build' and 'install' phases consist mostly of > commands that were already run in your custom phase? > > Do you still think that "Install shared object before attempting to > build the package" is an accurate statement? > > I offered to change this comment. You have ignored my offer. It's impossible to change that comment, because it's in the commit log. That's yet another reason why the source code itself is a better place for documentation than the commit logs. Mark