| 1 |
On Thu, Oct 13, 2011 at 12:12 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
| 2 |
> Mike Frysinger posted on Thu, 13 Oct 2011 00:39:52 -0400 as excerpted: |
| 3 |
> |
| 4 |
>> i thought there was talk of an automatic @security set at some point, |
| 5 |
>> but not sure if that got anywhere. |
| 6 |
|
| 7 |
Marius (genone) added @security support along with the other sets in |
| 8 |
portage-2.2, and it's still supported. |
| 9 |
|
| 10 |
> Sets (other than @system and @world) aren't available in stable portage |
| 11 |
> yet. Are they even in ~arch? |
| 12 |
|
| 13 |
We migrate features to ~arch (which becomes stable) as soon as they're |
| 14 |
in a state that we're happy enough to support long-term. Bug 144480 [1] |
| 15 |
tracks issues related to sets. |
| 16 |
|
| 17 |
> I've been running the masked 2.2 in |
| 18 |
> ordered to have sets for so long it's beginning to feel like openrc all |
| 19 |
> over again, except now it's not even in ~arch, AFAIK. <sigh> |
| 20 |
|
| 21 |
FWIW, we've already got plans to bring support for /etc/portage/sets to |
| 22 |
~arch [2]. |
| 23 |
|
| 24 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=144480 |
| 25 |
[2] https://bugs.gentoo.org/show_bug.cgi?id=384061 |
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Zac |
Archives