On 9/17/05, maxim wexler <[EMAIL PROTECTED]> wrote: > > cat /etc/make.profile/make.defaults > > > > This will show you the default flags your system is > > using. To that you > > add make.conf and any package.use flags to get what > > the system will > > use for your package. > > /etc/make.profile is a link to > /usr/portage/default-linux/x86/2005.0 but there's a > newer dir ../2005.1. The packages file seems to have > been updated. Dare I delete the present link and point > it to the newer dir? Why did whatever code made the > original link(I didn't put it there) not make a new > one to the latest dir? That's what makes me hesitate.
I would not until you read up on this. I'm not qualified to say what all the issues might be. I personally leave the profile alone until the developers force my hand and make me move forward. Note that since USE flags change from profile to profile, reflecting what the dev's think is the best standard set, if you do nothing else and issue an emerge --newuse --pv --deep --update world you would find that many programs need to be rebuilt. Under the 'ain't broke, don't fix it' methodology, leave it alone until you know why it's important to move forward. > > > > > From there I just let my imagination drive things > > and see how it works > > out. Most of the time it's OK, but sometimes I've > > had to recompile > > packages 2, 3 or even 4 times to get features I'm > > interested in. > > But when you do it right the first time: priceless Yep - Mark -- gentoo-user@gentoo.org mailing list
