| 1 |
On Sat, 2012-05-05 at 21:20 -0500, Dale wrote: |
| 2 |
> Ben wrote: |
| 3 |
> > On 6 May 2012 08:29, Dale <rdalek1967@×××××.com> wrote: |
| 4 |
> >> I mentioned this once a long time ago. We expect things to stay the |
| 5 |
> >> same unless we do something to change them. If things change without us |
| 6 |
> >> doing the change, we tend to freak out a bit. We don't need any |
| 7 |
> >> freaking out. |
| 8 |
> > |
| 9 |
> > Sounds to me like it would be a good idea to make a new, more minimal profile. |
| 10 |
> > What do you guys think? |
| 11 |
> > |
| 12 |
> > Cheers, |
| 13 |
> > Ben | yngwin |
| 14 |
> > |
| 15 |
> > |
| 16 |
> |
| 17 |
> |
| 18 |
> |
| 19 |
> Me, I don't mind the change but please let us know if the current one is |
| 20 |
> changed. Why not put this in for the 2012 or 11 profile? Whatever |
| 21 |
> number comes next. That way the users will know to look and have to |
| 22 |
> change to the new profile. |
| 23 |
> |
| 24 |
> I usually do a emerge -uvaDN world before I change profiles, then |
| 25 |
> change the profile and repeat with -a. That is when I expect to see USE |
| 26 |
> flag changes and lots of other goodies that you devs do. :-) |
| 27 |
> |
| 28 |
> Someone mentioned a news item. That would work but maybe a new and |
| 29 |
> fancy profile would work too. Someone may want to make others changes |
| 30 |
> to while they are at it. |
| 31 |
> |
| 32 |
> Just a thought. |
| 33 |
> |
| 34 |
> Dale |
| 35 |
> |
| 36 |
> :-) :-) |
| 37 |
> |
| 38 |
|
| 39 |
1) Yes, create a new profile for this change. |
| 40 |
|
| 41 |
2) Create a news item stating the change in default behavior for this |
| 42 |
new profile. |
| 43 |
|
| 44 |
3) mention the tools available to help with migrating this change. (see |
| 45 |
below) |
| 46 |
|
| 47 |
|
| 48 |
I created enalyze in gentoolkit for helping migrate changes like this |
| 49 |
without breaking systems. It is also very useful for lost/broken |
| 50 |
package.{use,keywords} files. Both the analyze and rebuild sub-modules |
| 51 |
of enalyze can show you how use flags are used for installed packages on |
| 52 |
your system. The analyze module shows which flags are default/not and |
| 53 |
the pkgs using them. It can help you decide what you want set in |
| 54 |
make.conf. The rebuild module can generate a new package.{use, |
| 55 |
keywords} file for you after considering the defaults and make.conf. In |
| 56 |
this case for making profile or make.conf use flag changes so that |
| 57 |
everything already installed will remain the same on your system for |
| 58 |
upgrades/re-installs. |
| 59 |
|
| 60 |
-- |
| 61 |
Brian Dolbec <dolsen@g.o> |
Archives