On Sat, 2012-05-05 at 21:20 -0500, Dale wrote: > Ben wrote: > > On 6 May 2012 08:29, Dale <rdalek1...@gmail.com> wrote: > >> I mentioned this once a long time ago. We expect things to stay the > >> same unless we do something to change them. If things change without us > >> doing the change, we tend to freak out a bit. We don't need any > >> freaking out. > > > > Sounds to me like it would be a good idea to make a new, more minimal > > profile. > > What do you guys think? > > > > Cheers, > > Ben | yngwin > > > > > > > > Me, I don't mind the change but please let us know if the current one is > changed. Why not put this in for the 2012 or 11 profile? Whatever > number comes next. That way the users will know to look and have to > change to the new profile. > > I usually do a emerge -uvaDN world before I change profiles, then > change the profile and repeat with -a. That is when I expect to see USE > flag changes and lots of other goodies that you devs do. :-) > > Someone mentioned a news item. That would work but maybe a new and > fancy profile would work too. Someone may want to make others changes > to while they are at it. > > Just a thought. > > Dale > > :-) :-) >
1) Yes, create a new profile for this change.
2) Create a news item stating the change in default behavior for this
new profile.
3) mention the tools available to help with migrating this change. (see
below)
I created enalyze in gentoolkit for helping migrate changes like this
without breaking systems. It is also very useful for lost/broken
package.{use,keywords} files. Both the analyze and rebuild sub-modules
of enalyze can show you how use flags are used for installed packages on
your system. The analyze module shows which flags are default/not and
the pkgs using them. It can help you decide what you want set in
make.conf. The rebuild module can generate a new package.{use,
keywords} file for you after considering the defaults and make.conf. In
this case for making profile or make.conf use flag changes so that
everything already installed will remain the same on your system for
upgrades/re-installs.
--
Brian Dolbec <dol...@gentoo.org>
signature.asc
Description: This is a digitally signed message part
