| 1 |
On 02/27/2011 10:14 AM, Sven Vermeulen wrote: |
| 2 |
> On Sun, Feb 27, 2011 at 10:05:28AM -0500, Anthony G. Basile wrote: |
| 3 |
>> Since the selinux policies come as a set with the same date as a version |
| 4 |
>> number, wouldn't it be better to, say, remove all the 20080525 first. |
| 5 |
>> Fix any brokenness, then deal with 20090730, etc until we've removed the |
| 6 |
>> sets we want gone? |
| 7 |
> |
| 8 |
> I was first thinking of cleaning up everything except the latest 2.20101213 |
| 9 |
> ebuilds, but if we remove any stable policy package and we have 1 user that |
| 10 |
> has that stable package installed, then his next world update will fail. By |
| 11 |
> not touching the latest stable ebuild (until the 2.20101213's stabilize) we |
| 12 |
> at least are more confident that that won't happen. |
| 13 |
> |
| 14 |
> Wkr, |
| 15 |
> Sven Vermeulen |
| 16 |
|
| 17 |
How does stabilization proceed for selinux? Has a precedence been set? |
| 18 |
There's over 200 packages. It cannot be done individually. |
| 19 |
|
| 20 |
If we're going to clean up everything except 2.20101213, then let's get |
| 21 |
them stabilized first and remove all the others. |
| 22 |
|
| 23 |
-- |
| 24 |
Anthony G. Basile, Ph.D. |
| 25 |
Gentoo Developer |
Archives