public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Feature request: package.use.stable.mask and package.use.stable.force
Date: Fri, 27 Apr 2012 19:55:54 +0200	[thread overview]
Message-ID: <201204271956.05754.dilfridge@gentoo.org> (raw)
In-Reply-To: <4F9ABAB8.5040602@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1907 bytes --]

Am Freitag 27 April 2012, 17:26:48 schrieb Zac Medico:
> > 
> > Maybe I'm missing something, but what would happen when the newest
> > version of a package is marked stable? The masked USE flags would
> > become unavailable for everyone?
> 
> In order to be practical, I guess we'd have to add a constraint which
> says that if KEYWORDS contains the stable variant of a particular
> keyword, then it should also be considered to implicitly contain the
> unstable variant when the package manager is deciding whether or not to
> apply package.use.{mask,force}.
> 
> So, here's a description of the whole algorithm that I'd use:
> 
> 1) Let EFFECTIVE_KEYWORDS equal the set of values contained in KEYWORDS,
> plus ** and all the unstable variants of the stable values contained in
> KEYWORDS. For example:
> 
>    KEYWORDS="~amd64 x86" -> EFFECTIVE_KEYWORDS="~amd64 x86 ** ~x86"
> 
> 2) Intersect EFFECTIVE_KEYWORDS with effective ACCEPT_KEYWORDS, where
> effective ACCEPT_KEYWORDS includes any relevant values from
> package.accept_keywords. For example, here is a table of intersections
> of EFFECTIVE_KEYWORDS="~amd64 x86 ** ~x86" with various effective
> ACCEPT_KEYWORDS values:
> 
>       ACCEPT_KEYWORDS  |  INTERSECTION  |  package.stable
>      -----------------------------------------------------
>       x86              |  x86           |  yes
>       x86 ~x86         |  x86 ~x86      |  no
>       **               |  **            |  no
>       amd64 ~amd64     |  ~amd64        |  no
> 
> 3) Apply package.stable settings if INTERSECTION contains only stable
> keywords. For example, see the package.stable column in the table above.


That is the best description I've seen so far, which exactly describes the use 
case that I had in mind.  +1 :)


-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-04-27 17:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 22:03 [gentoo-dev] Feature request: package.use.stable.mask and package.use.stable.force Andreas K. Huettel
2012-04-27  1:02 ` Mike Frysinger
2012-04-27  4:43 ` [gentoo-dev] " Jonathan Callen
2012-04-27  6:28   ` Mike Frysinger
2012-04-27  6:48     ` Zac Medico
2012-04-27  7:30       ` Zac Medico
2012-04-28 21:17         ` Mike Frysinger
2012-04-28 21:29           ` Zac Medico
2012-04-27  9:30 ` [gentoo-dev] " Michael Haubenwallner
2012-04-27 18:08   ` Andreas K. Huettel
2012-04-27 10:36 ` Ciaran McCreesh
2012-04-27 11:35   ` Chí-Thanh Christopher Nguyễn
2012-04-27 13:49     ` Ulrich Mueller
2012-04-27 15:26       ` Zac Medico
2012-04-27 17:55         ` Andreas K. Huettel [this message]
2012-04-27 19:25         ` [gentoo-dev] " Jonathan Callen
2012-04-27 19:36           ` Zac Medico
2012-04-27 19:57         ` [gentoo-dev] " David Leverton
2012-04-27 23:37           ` Zac Medico
2012-04-27 15:00     ` Rich Freeman
2012-04-27 18:01     ` Andreas K. Huettel
2012-04-27 14:31 ` Ian Stakenvicius
2012-04-27 18:03   ` Andreas K. Huettel

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=201204271956.05754.dilfridge@gentoo.org \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-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