public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
Cc: Gentoo Development <gentoo-dev@lists.gentoo.org>,
	 Gentoo Council <council@gentoo.org>
Subject: Re: [gentoo-dev] Extending EAPI="4"
Date: Mon, 29 Nov 2010 00:07:33 +0200	[thread overview]
Message-ID: <4CF2D2A5.1040209@gentoo.org> (raw)
In-Reply-To: <201011282256.54380.Arfrever@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

On 11/28/2010 11:56 PM, Arfrever Frehtes Taifersar Arahesis wrote:
>>
>> It seems like the problem here is that we don't have separate profiles
>> for stable and unstable keywords. The obvious solution would be to have
>> separate profiles, mask the flags in the stable profiles, and unmask the
>> flags in the unstable profiles. That way, repoman would continue to
>> protect stable profile users from unsatisfiable dependencies, without
>> unnecessarily masking those choices from unstable profile users.
> 
> I would prefer small number of additional files instead of huge proliferation of profiles.
> You also suggested using EAPI="4"-specific profiles instead of EAPI-versioned files, so eventually
> we might have about 4 times more profiles :) .
> 

There's no requirement to keep old profiles around indefinitely. Old
profiles will eventually go away once the new ones are the recommended
option. As for this particular case I haven't really taken a close
enough opinion to say if new profiles make the best sense or not.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  parent reply	other threads:[~2010-11-28 22:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 13:24 [gentoo-dev] Extending EAPI="4" Arfrever Frehtes Taifersar Arahesis
2010-10-25 13:42 ` Ciaran McCreesh
2010-10-25 13:56   ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 14:03     ` Ciaran McCreesh
2010-10-25 15:03       ` Arfrever Frehtes Taifersar Arahesis
2010-11-15 20:17       ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 13:56 ` Ulrich Mueller
2010-10-25 14:03   ` Ciaran McCreesh
2010-10-25 14:05   ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 14:43 ` Fabio Erculiani
2010-10-25 15:00   ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 16:12   ` Thomas Sachau
2010-10-25 16:23 ` Petteri Räty
2010-10-25 16:32   ` Diego Elio Pettenò
2010-10-25 16:44   ` Matti Bickel
2010-11-19 15:51 ` Zac Medico
2010-11-28 18:15   ` Arfrever Frehtes Taifersar Arahesis
2010-11-28 19:59     ` Zac Medico
2010-11-28 20:07       ` Arfrever Frehtes Taifersar Arahesis
2010-11-28 20:30         ` Zac Medico
2010-11-28 21:56           ` Arfrever Frehtes Taifersar Arahesis
2010-11-28 22:06             ` Zac Medico
2010-11-28 22:07             ` Petteri Räty [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-06 13:52 Arfrever Frehtes Taifersar Arahesis

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=4CF2D2A5.1040209@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=Arfrever@gentoo.org \
    --cc=council@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