From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id C9D4B6FFEC for ; Wed, 16 Dec 2015 09:56:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id tBG9uCqS010169; Wed, 16 Dec 2015 09:56:12 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CYPx_ncS62qQ; Wed, 16 Dec 2015 09:56:12 +0000 (GMT) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id tBG9u8xi010164 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 16 Dec 2015 09:56:09 GMT Message-ID: <1450259768.13505.99.camel@linuxfoundation.org> From: Richard Purdie To: Otavio Salvador Date: Wed, 16 Dec 2015 09:56:08 +0000 In-Reply-To: References: <1450218466.13505.95.camel@linuxfoundation.org> X-Mailer: Evolution 3.16.5-1ubuntu3.1 Mime-Version: 1.0 Cc: openembedded-core Subject: Re: [PATCH] m4: Drop unused/unreferenced patch X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2015 09:56:17 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2015-12-15 at 22:13 -0200, Otavio Salvador wrote: > On Tue, Dec 15, 2015 at 8:27 PM, Richard Purdie > wrote: > > Signed-off-by: Richard Purdie > > Is there a way to have a task, like fetchall, which checks for > non-referenced metadata files? This would help to avoid this to > happen > in future. Its a nice idea, the complexity is we have patches which can be native specific, libc specific, machine specific and so on. I guess if there were some bitbake API to pull out 'all possible overrides', we might be able to come up with a definitive list and do some checks based on that. Its not a simple problem and its also not a top priority issue right now with available resources. Might be an idea to open an enhancement bug for it though? Cheers, Richard