From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH] Clean all .go in clean-go
Date: Fri, 02 Sep 2016 14:42:27 +0200
Message-ID: <8737limq18.fsf@gnu.org>
References: <20160831232034.13748-1-ericbavier@openmailbox.org>
	<8760qgjugu.fsf@gnu.org> <874m5zokwp.fsf@gnu.org>
	<20160901203035.1ea32dee@openmailbox.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52065)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bfnnw-0007Ht-4z
	for guix-devel@gnu.org; Fri, 02 Sep 2016 08:42:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bfnnr-0006is-6o
	for guix-devel@gnu.org; Fri, 02 Sep 2016 08:42:43 -0400
In-Reply-To: <20160901203035.1ea32dee@openmailbox.org> (Eric Bavier's message
	of "Thu, 1 Sep 2016 20:30:35 -0500")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: guix-devel@gnu.org, Eric Bavier <bavier@member.fsf.org>

Eric Bavier <ericbavier@openmailbox.org> skribis:

> On Thu, 01 Sep 2016 14:37:58 +0200
> ludo@gnu.org (Ludovic Court=C3=A8s) wrote:

[...]

>> > In regards of the .go files remaining in the build directory, I agree
>> > that this is not good, however I don't think it is worth trying to fix
>> > this issue which equally applies to every file generated by Make.  Usi=
ng
>> > wildcards can be tempting in such cases but it can lead to accidental
>> > file deletions which is worse IMO.  As a consequence I would prefer
>> > keeping the current 'clean-go' rule.=20=20
>>=20
>> I sympathize with that.
>
> How about simply printing  a warning if there are any .go files laying
> around after a `make clean` or `make clean-go`?

Sure, why not.

Ludo=E2=80=99.