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 A4F631381F3 for ; Thu, 25 Jul 2013 23:47:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 11FDBE09C2; Thu, 25 Jul 2013 23:47:15 +0000 (UTC) Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 50BBFE098A for ; Thu, 25 Jul 2013 23:47:14 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id q55so1252038wes.16 for ; Thu, 25 Jul 2013 16:47:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ZdfLtUfZoEXOJlQL1nEeEgpIpx/7KJ1sIS908AoMxh0=; b=G4TdA74sSpLMlPSXidFX7ApJnA5DEixX3UzFfp/DTRJSEj2QTWu76oIHy1if+yKgHQ hL15EHZ1wceVJybSnTszUAo5GmuO+VVjuFDyHST4pIv571VeDSbNuwm7+6/3S3JVBa7V DSpqJfHXLsTuf3RygmghGfP3q9omyMOrMIKtlJIIGwg0nhd8JE/mZ4VzGVbDxnHkHnKU g5DSYO0sDbPVnh5dk9NKIairXzb24EawCVXKdwac8Tg2LnOJlJdmkxkpw1MaUcyjDXVd LFqDQ1u/nARLouuyLagCWNJ+DLrFRNEg6RvJQXsaOHwT+cQLnZDVPBkLQIPP7ZU58iFl SqsA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.180.11.146 with SMTP id q18mr3723802wib.50.1374796032983; Thu, 25 Jul 2013 16:47:12 -0700 (PDT) Sender: alex.alexander@gmail.com Received: by 10.194.0.142 with HTTP; Thu, 25 Jul 2013 16:47:12 -0700 (PDT) In-Reply-To: <51F17981.2010400@gentoo.org> References: <1374778444.4925.7.camel@localhost> <51F175BD.90601@gentoo.org> <1374779658.4925.17.camel@localhost> <51F17981.2010400@gentoo.org> Date: Fri, 26 Jul 2013 02:47:12 +0300 X-Google-Sender-Auth: zMNz8EC-rB-WZTmEGMDqBo0xHj8 Message-ID: Subject: Re: [gentoo-portage-dev] A way for trying to prevent useless rebuilds From: Alex Alexander To: gentoo-portage-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a11c24d162f4a9c04e25ea59e X-Archives-Salt: 6f3339ee-095e-4929-b888-eb9b32febbaa X-Archives-Hash: 4347594639e642c4eaecb3d24c7b382f --001a11c24d162f4a9c04e25ea59e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I once half-implemented something like this but never got to finish it, I'll try to dig up my code and check out its state. I recall using updates/ to tell portage what happened, which then updated the VDB to reflect the new state. On Thu, Jul 25, 2013 at 10:16 PM, Zac Medico wrote: > On 07/25/2013 12:14 PM, Pacho Ramos wrote: > > El jue, 25-07-2013 a las 12:00 -0700, Zac Medico escribi=F3: > >> On 07/25/2013 11:54 AM, Pacho Ramos wrote: > >>> This question comes to my mind every time a developer decides to > >>> drop/add a USE flag to ebuilds like gcc/webkit-gtk/libreoffice... > >>> > >>> I think that we should have a file (like used for category movements) > to > >>> let PM know how to handle this situation. > >>> > >>> For example, > >>> category/foo-1.0 has a "gnome" USE flag but, later, that one is > dropped: > >>> -> If it is now *enabling* that support always, our file could have > >>> something like: > >>> category/foo gnome + -> that would mean that, when "gnome" USE flag i= s > >>> NOT found, portage assumes it as being enabled, that will mean that > >>> people having previously "gnome" enabled wouldn't need to rebuild the > >>> package > >>> > >>> ... and the opposite > >>> > >>> What do you think? > >> > >> We could do something like that. You should propose it in the gentoo-p= ms > >> list. > > > > OK, wanted to be sure a similar idea wasn't rejected before :) > > I recall Brian Harring proposing something like that in the past, but it > never materialized. > -- > Thanks, > Zac > > --=20 Alex Alexander + wired + www.linuxized.com + www.leetworks.com --001a11c24d162f4a9c04e25ea59e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I once half-implemented something like this but never got = to finish it, I'll try to dig up my code and check out its state.
<= br>
I recall using updates/ to tell portage what happened, which = then updated the VDB to reflect the new state.


On Thu,= Jul 25, 2013 at 10:16 PM, Zac Medico <zmedico@gentoo.org> = wrote:
On 0= 7/25/2013 12:14 PM, Pacho Ramos wrote:
> El jue, 25-07-2013 a las 12:00 -0700, Zac Medico escribi=F3:
>> On 07/25/2013 11:54 AM, Pacho Ramos wrote:
>>> This question comes to my mind every time a developer decides = to
>>> drop/add a USE flag to ebuilds like gcc/webkit-gtk/libreoffice= ...
>>>
>>> I think that we should have a file (like used for category mov= ements) to
>>> let PM know how to handle this situation.
>>>
>>> For example,
>>> category/foo-1.0 has a "gnome" USE flag but, later, = that one is dropped:
>>> -> If it is now *enabling* that support always, our file co= uld have
>>> something like:
>>> category/foo gnome + -> that would mean that, when "gn= ome" USE flag is
>>> NOT found, portage assumes it as being enabled, that will mean= that
>>> people having previously "gnome" enabled wouldn'= t need to rebuild the
>>> package
>>>
>>> ... and the opposite
>>>
>>> What do you think?
>>
>> We could do something like that. You should propose it in the gent= oo-pms
>> list.
>
> OK, wanted to be sure a similar idea wasn't rejected before :)

I recall Brian Harring proposing something like that in the pas= t, but it
never materialized.
--
Thanks,
Zac




--
Alex Alexander
+ wired
+ www.linuxized.com
+ www.leetworks.com
--001a11c24d162f4a9c04e25ea59e--