1 |
On 06.07.2011 22:45, William Hubbs wrote: |
2 |
> On Wed, Jul 06, 2011 at 10:17:28PM +0300, Petteri Räty wrote: |
3 |
>> On 06.07.2011 21:55, William Hubbs wrote: |
4 |
>>> All, |
5 |
>>> |
6 |
>>> from my previous discussion, I am about to put a new virtual in the |
7 |
>>> tree. Do I need to use the same ~arch/30 day wait/stabilize cycle I |
8 |
>>> would normally use even though the default package the virtual will |
9 |
>>> bring in is stable everywhere? |
10 |
>>> |
11 |
>>> I'm thinking I can take the virtual straight to stable in this situation,, |
12 |
>>> but I want to be sure. |
13 |
>>> |
14 |
>> |
15 |
>> Nothing stable should be using the virtual at the time of commit so |
16 |
>> what's the benefit of going stable fast? Repoman should also be |
17 |
>> preventing commits straight to stable. I would stable the virtual at the |
18 |
>> same time as someone stable starts to use it (which probably means the |
19 |
>> 30 day period). |
20 |
> |
21 |
> Actually we could use it faster than that. I want to add a |
22 |
> virtual/service-manager (see http://bugs.gentoo.org/373843) for |
23 |
> sys-apps/openrc and sys-apps/systemd then add it to the system set, so |
24 |
> it would be used immediately everywhere. |
25 |
> |
26 |
> That will also make it possible for folks using systemd to remove |
27 |
> openrc from their systems if they want to do so, which they |
28 |
> can't right now because baselayout has a PDEPEND on openrc. |
29 |
> |
30 |
|
31 |
I don't see why one would need to hurry with changing the system set. On |
32 |
the contrary I would proceed more cautiously than usual. |
33 |
|
34 |
Regards, |
35 |
Petteri |