public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] A way for trying to prevent useless rebuilds
Date: Thu, 25 Jul 2013 12:00:13 -0700	[thread overview]
Message-ID: <51F175BD.90601@gentoo.org> (raw)
In-Reply-To: <1374778444.4925.7.camel@localhost>

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 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 gentoo-pms
list.
-- 
Thanks,
Zac


  reply	other threads:[~2013-07-25 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 18:54 [gentoo-portage-dev] A way for trying to prevent useless rebuilds Pacho Ramos
2013-07-25 19:00 ` Zac Medico [this message]
2013-07-25 19:14   ` Pacho Ramos
2013-07-25 19:16     ` Zac Medico
2013-07-25 23:47       ` Alex Alexander
2013-07-26  5:10         ` Pacho Ramos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51F175BD.90601@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox