From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What is the release date for 2006.1?
Date: Wed, 2 Aug 2006 17:40:17 -0700 [thread overview]
Message-ID: <7573e9640608021740i56bd4c26j9256b08cba152159@mail.gmail.com> (raw)
In-Reply-To: <20060803000928.GA6200@jfindlay.us>
On 8/2/06, Justin R Findlay <justin@jfindlay.us> wrote:
> So why should I bother manually changing the /etc/make.profile symlink?
Well the main reason is because profiles will disappear from portage
after a certain amount of time, and you can't really run without a
profile!!
The main effects changing the profile has for an existing install are:
1. Updates to default USE flags and masks.
2. Updates to make.defaults
3. Updates to virtual package defaults.
4. Updates to the system package set, or minimum versions of the
system packages.
> Does this link get moved when the "release" is ready?
Changing the profile can sometimes cause a lot of updates, changes to
use flags, features, etc, so no, it is not done automatically.
Generally after changing the make.profile link, you will want to do an
"emerge -DNuvp world" to see what changed.
HTH,
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-03 0:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 3:54 [gentoo-user] What is the release date for 2006.1? Jerônimo Backes
[not found] ` <200608021740.38576.germanobax@yahoo.com.br>
2006-08-02 21:38 ` Richard Fish
2006-08-03 0:09 ` Justin R Findlay
2006-08-03 0:40 ` Richard Fish [this message]
2006-08-03 0:48 ` Richard Fish
2006-08-03 3:55 ` Justin R Findlay
2006-08-03 4:09 ` Jesús Guerrero
2006-08-05 10:05 ` Critical task upgrades (was [gentoo-user] What is the release date for 2006.1?) David Corbin
2006-08-03 6:05 ` [gentoo-user] What is the release date for 2006.1? Alexander Skwar
2006-08-03 6:23 ` Donnie Berkholz
2006-08-03 6:30 ` Justin R Findlay
2006-08-03 15:56 ` Jesús Guerrero
2006-08-03 6:36 ` Iain Buchanan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7573e9640608021740i56bd4c26j9256b08cba152159@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox