| 1 |
On 01/01/2012 01:23 AM, Duncan wrote: |
| 2 |
> As for the switchover, I had already been thinking about it here and thus |
| 3 |
> have a couple ideas I'd very much like to see implemented in portage/PM/ |
| 4 |
> base.eclass that could definitely help, along with a USE flag. I'll call |
| 5 |
> them "migrated-rootfs" and "migrateroot-strict" for purposes of |
| 6 |
> discussion, here, and assume they're both portage features and that |
| 7 |
> migrated-rootfs is also a USE flag |
| 8 |
> |
| 9 |
> FEATURES=migrated-rootfs would set a USE-default for migrated-root-to-usr |
| 10 |
> so that it'd default to ON, and would indicate that a user is an "early |
| 11 |
> adopter" of the new layout, preferring migration as soon as possible. |
| 12 |
> Users could still set the USE flag as desired for specific packages, at |
| 13 |
> least at first, tho at some point it'd probably first be made a profile |
| 14 |
> default, and ultimately profile-masked either on or off. |
| 15 |
|
| 16 |
I'm not sure if a USE flag for FEATURES setting would be necessary. If |
| 17 |
we want to enforce a global policy, then I guess a QA warning would be |
| 18 |
warranted. |
| 19 |
|
| 20 |
Overall, a migration like this should go pretty smoothly as long as |
| 21 |
people with separate /usr take appropriate actions to make sure their |
| 22 |
systems will boot. People without separate /usr can basically relax and |
| 23 |
enjoy the ride. |
| 24 |
-- |
| 25 |
Thanks, |
| 26 |
Zac |
Archives