From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 059FC1381F3 for ; Mon, 17 Jun 2013 19:38:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1763CE096B; Mon, 17 Jun 2013 19:38:38 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 34099E0933 for ; Mon, 17 Jun 2013 19:38:37 +0000 (UTC) Received: from [192.168.1.33] (194.Red-2-137-19.dynamicIP.rima-tde.net [2.137.19.194]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id A0FF333E532; Mon, 17 Jun 2013 19:38:34 +0000 (UTC) Message-ID: <1371497910.22480.22.camel@localhost> Subject: Re: [gentoo-dev] How to spread intltool fixes to all packages From: Pacho Ramos To: Mike Frysinger Cc: gentoo-dev@lists.gentoo.org, "gnome@gentoo.org" Date: Mon, 17 Jun 2013 21:38:30 +0200 In-Reply-To: <201306170105.42908.vapier@gentoo.org> References: <1370944514.4583.28.camel@localhost> <201306170105.42908.vapier@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: e796d500-21ec-479f-9292-8ae4b25bb6cb X-Archives-Hash: 0e6119f05ed378617ec14864fa16b94c El lun, 17-06-2013 a las 01:05 -0400, Mike Frysinger escribió: [...] > ELT-PATCHES is only used by elibtoolize which means it requires an explicit > call to patch things > > you're basically talking about the same type of problem that > https://bugs.gentoo.org/220040 tried to address. maybe we should update > autotools.eclass to have a general patching mechanism since any EAPI based one > is doomed to failure. and then we rebase elibtoolize to that. > -mike It looks a bit ambitious to me, but, if you think it is not so hard to do, would be interesting :O