public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] A way for trying to prevent useless rebuilds
Date: Sat, 27 Jul 2013 00:31:40 +0200	[thread overview]
Message-ID: <1374877900.1020.3.camel@localhost> (raw)
In-Reply-To: <20130727002201.299cf897@gentoo.org>

El sáb, 27-07-2013 a las 00:22 +0200, Michał Górny escribió:
> I'd go for reusing USE dependency defaults syntax, that is:
> 
>   category/foo gnome(+)
> 
> and:
> 
>   category/foo gnome(-)

Nice, I was thinking in that syntax when suggesting this ;)

> 
> And honestly, I have no idea how safe is that. We'd probably need
> version ranges to use it effectively and safely, e.g.
> 
>   ~category/foo-2..4 gnome(+)
> 

I think this only makes sense when a USE flag is changed without
bump/revbump as, otherwise, people will get a rebuild anyway, then:
=category/foo-1.x gnome(+)

should work

> No idea if and how this should interact with USE dependency defaults
> in other packages.
> 
> Ciaran will probably have more doubts.
> 

I have seen sometimes people suggesting to manually edit VDB to change
the USE flag if wanting to prevent rebuild (I remember this hack for a
change in USE flags that affected a ton of kde related packages years
ago). My idea would be that this "editing" should be done by portage (or
PM) and, then, this should be a two steps process:
1. First one should be used to change VDB
2. Second one would be to do the usual dep calculation with new VDB
information




      reply	other threads:[~2013-07-26 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 19:15 [gentoo-pms] A way for trying to prevent useless rebuilds Pacho Ramos
2013-07-26 22:22 ` Michał Górny
2013-07-26 22:31   ` Pacho Ramos [this message]

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=1374877900.1020.3.camel@localhost \
    --to=pacho@gentoo.org \
    --cc=gentoo-pms@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